For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Help CenterOpenAPI SpecStatus
OverviewInquiriesTransactionsAPI ReferenceChangelog
OverviewInquiriesTransactionsAPI ReferenceChangelog
  • Getting Started
    • Introduction
    • Quickstart Tutorial
  • API Overview
    • API Keys
    • Authentication
    • Protocol
    • Response Body
    • Idempotence
    • Pagination
    • Rate Limiting
    • Downloading Files
    • API Logs
    • Request IDs
  • Versioning
    • API Changelog
    • Versioning
  • Troubleshooting
    • Error Handling
  • API Reference
    • OpenAPI Specification
    • Cases
    • Connect
    • Documents
    • Inquiries
    • List Items
    • Lists
    • OAuth
    • Reports
    • Transactions
    • Verifications
    • Workflows
  • Webhooks
LogoLogo
Help CenterOpenAPI SpecStatus
On this page
  • Encoding query string values
API Overview

Protocol

The Persona API uses GET, POST, PATCH, and DELETE requests to communicate and HTTP response codes to indicate status and errors. All responses come in standard JSON. The Persona API is served over HTTPS TLS v1.2+ to ensure data privacy; HTTP and HTTPS with TLS versions below 1.1 are not supported. Requests should typically include a Content-Type of application/json and the body must be valid JSON. Exceptions are for uploading files for some APIs, where you can use a Content-Type of multipart/form-data.

Encoding query string values

When passing query string arguments, please be sure to make values URL-safe, e.g. with encodeURIComponent in JavaScript. For example, if passing a phone number with an area code, '%2B1...' should be passed instead of '+1...'.

Was this page helpful?
Previous

Response Body

Next
Built with