Skip to main content
API authentication
Search
Search SafeSend Help and Support.

This article applies to:

  • Product: safesend
  • Subject: API

Call a SafeSend API with an M2M access token

Include a Thomson Reuters M2M bearer token and an authorized SafeSend user email address in each SafeSend API request.
Generate a valid M2M access token before you call a SafeSend API.
  1. Add the M2M access token to the
    Authorization
     request header.
    Specify the token by using the following format:
    Bearer <ACCESS_TOKEN>
    .
  2. Add the email address of an authorized SafeSend user to the
    x-email
     request header.
    important
    All SafeSend API endpoints require the
    x-email
     header. Use the email address of the SafeSend user who makes the API call.
  3. Send the API request.
Example: Upload a return by using the SSR Returns Post Upload API
POST "https://api.safesend.com/ssr/v2/return/upload" \
--header "Authorization: Bearer <ACCESS_TOKEN>" \
--header "Content-Type: application/json" \
--header "x-email: <X_EMAIL>" \
--data '{
  "documents": [
    "string"
  ],
  "fileURLs": [
    "string"
  ],
  "correlationId": "string",
  "rid": "string",
  "clientId": "string",
  "delayRecognition": false,
  "taxSoftware": 0,
  "callbackUri": "string"
}'
The API validates both the M2M access token and the SafeSend user identified in the
x-email
 header.

error-icon

error-close