API authentication, endpoints, and error handling for Answering Service Care.
Use Answering Service Care APIs to connect external systems with messages, call recordings, and To Dos in your account.
This page covers shared setup, integration context, and where each API fits operationally.
Use the endpoint pages for request bodies, response schemas, examples, and field-level details.
Send requests to the secure Answering Service Care host. Use this base URL for every API request.
https://secure.answeringservicecare.comAnswering Service Care uses bearer token authentication.
Generate API tokens from your user profile under Application Keys.
Use API tokens for internal integrations, reporting workflows, and system-to-system access.
You can create new tokens, review active tokens, and revoke tokens that are no longer needed.
If you manage more than one integration, use separate tokens so rotation and revocation stay easier to manage.
Accept: application/json
Content-Type: application/json
Authorization: Bearer {AUTH_TOKEN}Use the Messages API when another system needs message history, message status, or message-level actions.
This is the main API for retrieving message records and syncing message state.
Related pages:
Messages
List Messages
Get a Message
Update a Message
Use the Call Recordings API when you need audio files and call detail data for QA, compliance review, dispute research, or archival workflows.
Call recordings are retained for up to 31 days.
Related pages:
Call Recordings
List Call Recordings
Get a Call Recording
Use the To Dos API to create and retrieve scheduled outbound tasks across SMS, email, and call workflows.
This supports reminder programs, follow-up workflows, and recurring outbound communication.
Related pages:
List To Dos
Create a To Do
Answering Service Care APIs use REST endpoints and return JSON responses.
Requests are stateless and authenticated with bearer tokens.
Most integrations follow this pattern:
generate a token in Answering Service Care
send authenticated requests to https://secure.answeringservicecare.com
store or process the returned data in your internal system
Supported delivery types:
sms
email
call
401
Unauthorized
422
Missing or invalid parameter
400
Processing error
Log both the status code and response body in your integration.
That makes token, validation, and payload issues much easier to troubleshoot.
Last updated
Was this helpful?
Was this helpful?
GET /api/v2/messages
GET /api/v2/messages/{id}GET /api/v2/call-recordings
GET /api/v2/call-recordings/{id}GET /api/v2/to-dos
POST /api/v2/to-dos