API Authentication

API Environments

There are two API environments available to you:

EnvironmentsDescription
SandboxUsed to build out and test your integration.
ProductionYour live environment that will initiate real interactions with government entities. Usage is billed in the environment.


Retrieve your API keys

Log in or create an account with the Abound Dashboard to find and retrieve your API keys.

API keys are environment specific and can be found on the Keys page.


Authenticating API requests

Authentication requires passing your bearer token for the desired environment (sandbox or production) in the Authorization header of your API request.

The bearer token is in the period-delimited format of: appId.appSecret


The following is an example request that lists all TIN Verifications with the required Authorization header.

1curl \
2  --request GET \
3  --url https://sandbox-api.withabound.com/v4/tin-verifications \
4  --header 'Accept: application/json'
5  --header 'Authorization: Bearer appId_sampleqNhVcdYQYU.appSecret_sampleMz2Zbj3Hq'
ValueDescription
appIdA non-sensitive, public identifier that is used to identify your app.
appSecretA sensitive, private key used to make secure calls to the Abound from your backend. Your appSecret should never be shared on the client-side or stored directly in your code.
https://sandbox-api.withabound.com/v4Sandbox API environment; use test credentials and build out and test your integration.
https://production-api.withabound.com/v4Production API environment; this environment is billed and will initiate real interactions with government entities.