Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.kyckr.com/llms.txt

Use this file to discover all available pages before exploring further.

The Kyckr sandbox is a dedicated test environment that mirrors the full functionality of the production API. You can complete the entire integration journey — searching for companies, retrieving profiles, ordering filings — without incurring charges or touching live registry data.
The sandbox covers the V2 REST API only. If you are working with V1, refer to the V1 documentation.

What the sandbox supports

The sandbox is designed to let you validate the complete end-to-end flow your integration will rely on in production:
CapabilityAvailable in sandbox
Company search by name
Company search by registration number
Lite Profile retrieval
Enhanced Profile retrieval✓ (select jurisdictions)
Filing list retrieval
Filing document download✓ (blank PDF returned)
Order history (/orders)✓ (fixed response, see note below)

Connecting to the sandbox

The sandbox uses a separate base URL from the production environment. Use your sandbox credentials when making requests.
# Base URL — sandbox
https://test-api.kyckr.com/v2
All endpoints, request formats, and response schemas are identical to production. No changes to your request structure are needed when switching environments.

Known differences from production

Keep the following in mind when building against the sandbox. These are intentional design choices, not bugs. Name search behaviour. When searching by company name, the sandbox returns all companies available for the selected country, regardless of the search term you provide. This is expected behaviour — do not rely on search-term filtering when writing sandbox tests. Performance Response times in the sandbox are not representative of production. Do not use sandbox performance as a benchmark for SLA planning or latency estimates. Filing documents The /companies/{kyckrId}/documents endpoint returns a valid list of available filings for any sandbox company. However, the PDF returned on download is always a blank document. This is sufficient to test the ordering and retrieval flow end-to-end. Order history The /orders endpoint always returns the same fixed list of orders. Querying for a specific order ID is not supported in the sandbox.

Available jurisdictions

Lite Profile and Enhanced Profile

The following jurisdictions have full Lite and Enhanced Profile data available:
CountryCode
AustraliaAU
AustriaAT
BelgiumBE
ChinaCN
DenmarkDK
EstoniaEE
FranceFR
GermanyDE
IndiaIN
IrelandIE
ItalyIT
LuxembourgLU
NetherlandsNL
New ZealandNZ
SingaporeSG
SpainES
United Arab EmiratesAE
United KingdomGB
United States — FloridaUS-FL
United States — New YorkUS-NY

Lite Profile only

The following jurisdictions return Lite Profile data only. Enhanced Profile is not available for these in the sandbox.
CountryCode
Canada (all provinces)CA-ALL
Canada — OntarioCA-ON
Canada — QuebecCA-QC
SwitzerlandCH

Work through the following sequence to validate your integration before moving to production.
1

Search for a company

Use /companies/search with a supported jurisdiction code. Confirm that results are returned and that the response structure matches your expected schema.
2

Retrieve a Lite Profile

Use the kyckrId from your search result to call /companies/{kyckrId}/lite. Verify the fields your integration depends on are present and correctly typed.
3

Retrieve an Enhanced Profile

Call /companies/{kyckrId}/enhanced for a jurisdiction that supports it (see table above). Check that the representatives and shareholders arrays are populated as expected.
4

List available filings

Call /companies/{kyckrId}/documents to retrieve the filing list. Confirm the response structure and that document metadata is present.
5

Download a filing

Order and download a filing document. Verify your pipeline handles the PDF response correctly. The file returned will be blank — this is expected.
6

Review order history

Call /orders to confirm your order history logic handles the fixed sandbox response without errors.

Moving to production

Once you have validated your integration in the sandbox, switch to your production credentials and update the base URL. No other changes to your request structure are required. If you do not yet have production credentials, request access via the Kyckr demo page.