Skip to main content
POST
Create a new customer session

Authorizations

Authorization
string
header
required

Basic HTTP authentication. Allowed headers-- Authorization: Basic <base64(api_key_id:api_key_secret)>

Body

application/json
partner_customer_id
string

The unique identifier for the customer in the partner's system.

Compared byte-for-byte, so PARTNER_USER_456 and partner_user_456 are two different customers. Send the same casing everywhere or a later lookup silently returns no match.

Restricted to printable ASCII (\x20\x7E) rather than arbitrary UTF-8: the value is propagated between internal services as an HTTP/2 header, which cannot carry non-ASCII bytes. The bound is published rather than discovered.

Required string length: 1 - 128
Pattern: ^[\x20-\x7E]+$
Example:

"PARTNER_USER_456"

transaction_amount
integer

The current transaction amount, if the session is currently executing a transaction. integer value in the min currency unit (cents for USD)

Example:

34000

transaction_currency
string

The 3 char currency code of the amount in iso-4217

Example:

"USD"

customer_history
object

A Customer's account history with the partner

source
string

The marketing source that referred the customer.

Example:

"web_signup"

utm_medium
string

The marketing medium that referred the customer.

Example:

"cpc"

utm_campaign
string

The marketing campaign that referred the customer.

Example:

"spring_card_launch"

utm_content
string

The specific creative or placement that referred the customer.

Example:

"hero_banner_v2"

utm_term
string

The paid search keyword that referred the customer.

Example:

"rewards+credit+card"

utm_owner
string

The team or owner accountable for the campaign that produced this session.

Example:

"growth"

application_origin
enum<string>

Where the application was physically initiated.

Available options:
in_store_associate,
in_store_kiosk,
in_store_signage
Example:

"in_store_kiosk"

origin_location_id
string

Your own store or location code identifying where the application originated.

Example:

"STORE-4417"

metadata
object

Additional linking metadata

Example:
customer_metadata
object

A set of key-value pairs attached to the customer. These values will be included in webhook event payloads for the partner to receive information about the customer.

Example:

Response

Customer session created successfully

Represents a session created on behalf of an Imprint customer

id
string
required

The unique ID Imprint assigns to the session.

Example:

"2EE24580-B97B-4949-A65C-929CCB9B9B8D"

client_secret
string
required

Not to be logged or stored. Provide this one time use token to the Imprint SDK or other client side code to allow the customer access to edit their own account or apply

Example:

"QzMyNzg4QzgtNEUwOS00QkU4LThDMjEtMkU5OUQ3QzkwRDhGCg=="

expires_at
string
required

the RFC-3339 timestamp when the client_secret will expire.

Example:

"2025-02-13T19:08:07.000Z"

metadata
object

Set of key-value pairs for storing additional information about the customer session.

Example:
customer_metadata
object

A set of key-value pairs attached to the customer. These values will be included in webhook event payloads for the partner to receive information about the customer.

Example:
source
string

The marketing source that referred the customer.

Example:

"web_signup"

utm_medium
string

The marketing medium that referred the customer.

Example:

"cpc"

utm_campaign
string

The marketing campaign that referred the customer.

Example:

"spring_card_launch"

utm_content
string

The specific creative or placement that referred the customer.

Example:

"hero_banner_v2"

utm_term
string

The paid search keyword that referred the customer.

Example:

"rewards+credit+card"

utm_owner
string

The team or owner accountable for the campaign that produced this session.

Example:

"growth"

application_origin
enum<string>

Where the application was physically initiated.

Available options:
in_store_associate,
in_store_kiosk,
in_store_signage
Example:

"in_store_kiosk"

origin_location_id
string

Your own store or location code identifying where the application originated.

Example:

"STORE-4417"

partner_customer_id
string

The unique identifier for the customer in the partner's system.

Compared byte-for-byte, so PARTNER_USER_456 and partner_user_456 are two different customers. Send the same casing everywhere or a later lookup silently returns no match.

Restricted to printable ASCII (\x20\x7E) rather than arbitrary UTF-8: the value is propagated between internal services as an HTTP/2 header, which cannot carry non-ASCII bytes. The bound is published rather than discovered.

Required string length: 1 - 128
Pattern: ^[\x20-\x7E]+$
Example:

"PARTNER_USER_456"

transaction_amount
integer<int64>

The current transaction amount, in the min currency unit (cents for USD)

Example:

34000

transaction_currency
string

The 3 char currency code of the amount in iso-4217

Example:

"USD"

customer_history
object

A Customer's account history with the partner