Skip to content

Validate Sandbox Token

During the development of your integration, you will want to validate and check if the JWT token you are generating is valid. This endpoint allows you to check that a JWT your system has generated is valid. This endpoint only works with your SANDBOX credentials - LIVE credentials will be rejected.

Endpoint

  • Base Url: https://poweredby.dosh.com
  • Path: /api/auth/token/validate-sandbox
  • Method: POST
  • Content-Type: application/json

Request Body Format

Field Required Example Description
secretKey Yes 4b990ed8-fde8-4409-9aa7-d710e44cf66b This is the Secret Key used to sign the JWT token.
token Yes eyJhbGciOiJIUzI1NiIsIn... The generated JWT token that need to be validated towards Powered By auth mechanism 
1
2
3
4
{
  "secretKey": "4b990ed8-fde8-4409-9aa7-d710e44cf66b",
  "token": "eyJhbGciOiJIUzI1NiIsIn..."
}

Security

The endpoints you expose and that Cardlytics exposes are available over the public internet. To validate that the request originated from an authenticated client, all requests include a JWT which attests to the authenticity of the request. For more details, see: the API Reference: Overview: Cardlytics JWT Authorization Token.

HTTP Conventions

Cardlytics's API endpoints and webhooks all try to adhere to and honor standard HTTP status codes. Below are the response codes that you may see when calling Cardlytics's endpoints and webhooks.

  • 200 OK - Success. The request is understood and acknowledged. The body of the response may indicate additional context or error conditions.
  • 301 and 302 - Cardlytics does not currently require clients to handle redirects. For future proofing, following 1 redirect for a request to Cardlytics is recommended.
  • 401 Unauthorized - Will be returned when the request does not include required credentials.
  • 403 Forbidden - Will be returned when the caller is not allowed to invoke the endpoint.
  • 404 Not Found - Will be returned when Cardlytics cannot locate the resource requested.
  • 405 Method Not Allowed - Will be returned when Cardlytics does not support the HTTP method requested. Note that most Cardlytics endpoints support POST only.
  • 415 Unsupported Media Type - Will be returned when Cardlytics does not understand the body of the request. Note that most Cardlytics endpoints support application/json only.
  • 429 Too Many Requests - Will be returned when Cardlytics is throttling requests from your client. Note that Cardlytics tries to never respond with this response code but may under extreme circumstances.
  • 500 Internal Server Error - Will be returned when Cardlytics emits an unknown or not-handled error.
  • 501 Not Implemented - Will be returned when Cardlytics completely does not understand the request passed.
  • 503 Service Unavailable - Will be returned if the specific service is down for maintenance or other reasons.