Skip to main content
This guide walks you through authenticating with the SOLO Network API and making your first query.

​
Prerequisites

  • A SOLO Network account with API credentials
  • An SDK token (provided by your SOLO account manager)

​
1. Authenticate

All API requests require a Bearer token in the Authorization header. You’ll use the SDK token issued for your integration. 
export SOLO_TOKEN="your-sdk-token-here"

​
2. Make your first query

Let’s query identity prefill data for a consumer. This retrieves any existing identity data the network has for the given identifiers. 
curl -X POST https://api.solo.one/api/templates/identity_prefill/query \
  -H "Authorization: Bearer $SOLO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "consumer_first_name": "Jane",
    "consumer_last_name": "Doe",
    "consumer_date_of_birth": "1990-01-15",
    "consumer_ssn_last_four": "1234"
  }'

​
3. Furnish data

Once you’ve collected verification data, you can furnish it back to the network. This makes the data available for future queries by authorized participants. 
curl -X POST https://api.solo.one/api/templates/identity_prefill/furnish \
  -H "Authorization: Bearer $SOLO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "consumer_first_name": "Jane",
    "consumer_last_name": "Doe",
    "consumer_date_of_birth": "1990-01-15",
    "consumer_ssn_last_four": "1234",
    "consumer_address_line_1": "123 Main St",
    "consumer_address_city": "San Francisco",
    "consumer_address_state": "CA",
    "consumer_address_zip": "94102"
  }'

​
4. Use a bundle

For common workflows, use a use case bundle instead of calling templates individually. For example, the KYC Certificate Bundle aggregates document capture, biometric checks, address verification, and liveness detection into a single call. 
curl -X POST https://api.solo.one/api/use_cases/templates/kyc_certificate_bundle \
  -H "Authorization: Bearer $SOLO_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "consumer_first_name": "Jane",
    "consumer_last_name": "Doe",
    "consumer_date_of_birth": "1990-01-15",
    "consumer_ssn_last_four": "1234"
  }'
The response includes data from all underlying templates along with completion status flags for each component.

​
What’s next?

Authentication

Learn about token types and scopes.

Templates

Understand how templates and the query/furnish pattern work.