Get credentials in the Hub, then use the get started API v1 or get started API v2 reference for authentication, request signing, errors, base URLs, and rate limits.
Solidgate APIs are available in two versions.
Authenticate with the channel Public and Secret keys and an HMAC-SHA512 signature on every request. Domain-specific hosts serve payments, subscriptions, checkout, reports, and risks.
Includes
Authenticate with a Bearer token. Keys can apply to the whole account or selected channels, with fine-grained permissions. All operations use one host and a consistent resource/action path pattern.
Includes
Overview
Full request and response contracts remain in the Solidgate API reference.
| API v1 | API v2 | |
|---|---|---|
| Authentication | merchant and signature headers.HMAC-SHA512 over publicKey + body + publicKey. | Authorization: Bearer with the API secret.No request signature. |
| API keys | Channel keys with prefixes api_pk_ / api_sk_. | Account or channel-bound keys with prefixes akey_ / asec_.Scopes by channel and permission. Zero-downtime rotation. |
| Host and path | Multiple hosts, for example pay.solidgate.com, gate.solidgate.com, subscriptions.solidgate.com. Action after /api/v1/. | Single host https://api.solidgate.com/v2. Pattern /{resources}/{action}. |
| HTTP method | Depends on the operation (POST, GET, and others). | POST for all operations. |
| Errors | Nested error object with numeric-style codes, for example 3.02. | Flat envelope with named codes, for example PERMISSION_DENIED, optional context, and a request-id header. |
| Webhooks | Validate with webhook Public and Secret keys using the same HMAC-SHA512 model as API requests. | Manage endpoints via API v2. Validate with the endpoint secret using HMAC-SHA256 in the signature header. |
| Best fit | Payment processing, Payment Page and Link, products and prices, Billing 1.0, classic reports and risk APIs. | New integrations on the unified v2 host, scoped API keys, platform management, and expanding product domains in the API Reference. |
Retrieve your credentials
To call the Solidgate API, even in the sandbox, you need credentials from the Solidgate Hub .
-
Solidgate
API v1
Public and Secret keys from Developers > channel details. Prefixesapi_pk_/api_sk_. Webhook keys usewh_pk_/wh_sk_. -
Solidgate
API v2
Create keys under Developers > API v2 > API keys. Prefixesakey_/asec_. Restrict by channel when needed.
- Go to Developers.
- Select the API version.
- For API v1: select the channel you need, then on the Channel details page find the API keys.
- For API v2: go to Keys, click on Create API key, name your keys and optionally select a channel or multiple channels, then click on Create.
- Copy your API key.
Generate signature
Request signing applies to
Solidgate
API v1
only. Build the HMAC-SHA512
generate signature
API v1
and send it with the merchant and signature headers.
Solidgate API v2 uses Bearer authentication and does not require a request signature.
Next steps
API logs
API logs capture request and response records in the Hub. Use them to troubleshoot issues, monitor traffic, and investigate unexpected API usage.
Search request and response body content directly on the API logs page. Combine body search with filters for status code, method, host, and date range to isolate a specific entry.
- Go to Developers > API logs.
- Enter a search query for terms or phrases in the request and response bodies.
- Use single terms, phrases, wildcards, or boolean logic (
AND,OR, exclude with-). - Optionally narrow results with Status, Method, Host, and date range filters.
- Use single terms, phrases, wildcards, or boolean logic (
- Find the log entry you need and click on it.
- View log entry details, including Status, Method, Path, Host, IP address, and Date (UTC).
- Expand Request body and Response body to see the JSON payloads sent and received.