Skip to main content

Apps

An app is an Inttegro account. It represents the business, seller, sales channel, tenant, or environment that is selling, collecting payments, messaging customers, and receiving payouts through Inttegro.

Everything that happens for that account belongs to its app: orders, customers, payment methods, balances, payouts, files, and customer messages. This keeps each business unit or tenant in its own operating boundary, so records, reconciliation, and access do not bleed across accounts.

Apps also have secret keys. When your backend uses a key, it is acting for that app. Use the Apps API when you need to create or manage Inttegro accounts programmatically: onboarding a merchant or tenant, separating production from staging, isolating a sales channel, or giving a child integration its own credentials. Do not create apps for individual shoppers, orders, devices, or checkout sessions.

Operations

The app object

An app object contains the stable identifier and human-readable metadata for one Inttegro account. Secret key values are not returned on normal app lookups; the initial token appears only in the response from Create an app.

Properties

  • Name
    alias
    Type
    string
    Description

    Optional short label for the app. Use this for names that are easier to scan in dashboards, logs, or developer tooling than the generated app ID.

  • Name
    archived_at
    Type
    timestamp
    Description

    When the app was archived. Omitted while the app is active.

  • Name
    created_at
    Type
    timestamp
    Description

    When the app was created.

  • Name
    description
    Type
    string
    Description

    Optional longer description of what the app is used for.

  • Name
    id
    Type
    string
    Description

    Unique identifier for the app. App IDs begin with the app_ prefix.

  • Name
    name
    Type
    string
    Description

    Display name for the app.

  • Name
    updated_at
    Type
    timestamp
    Description

    When the app metadata was last updated. Omitted until the first update.

POST/apps/create

Create an app

Create an Inttegro child app and its first secret key. Your current Inttegro account becomes its parent unless you supply separately authorized delegated placement details.

Store app.secret_key.token immediately after the response is received. The full token is returned only at creation time and is not included in later lookup or update responses.

Surrounding whitespace is removed from text attributes, and unknown attributes are rejected. name must remain non-empty after trimming. For legal_entity_type, use government, non_profit, business, or individual; integrations should not rely on undocumented classifications being accepted.

Omit placement_parent_application_id for ordinary child-app creation. Placing the child under another app requires a valid authorization receipt for that relationship and a compatible relationship_policy; a bare parent ID is rejected with 422.

Request attributes

  • Name
    alias
    Type
    string
    Description

    Optional short label for the app. The API trims surrounding whitespace before storing it.

  • Name
    description
    Type
    string
    Description

    Optional description of what the app is used for.

  • Name
    name
    Type
    string
    Required
    required
    Description

    Display name for the app. Must not be empty after trimming whitespace.

  • Name
    placement_parent_application_id
    Type
    string
    Description

    App under which to place the new child app. Omit this to use the app that authenticates the request. A different parent requires separately authorized delegated placement details.

  • relationship_policyobjectOptional policy for the parent-child app relationship. Omitted fields use the defaults shown below.Click or tap to expand
    • Name
      child_standing
      Type
      enum
      Description
      Standing of the child app. Supported values are controlled, temporary_setup, and independent. Defaults to controlled for parent-managed apps and independent for child-managed apps.
    • Name
      credentials
      Type
      enum
      Description
      Which app controls credentials. Supported values are child and parent. Defaults to child.
    • Name
      management
      Type
      enum
      Description
      Which app manages the relationship. Supported values are parent and child. Defaults to parent.

Response shape

A successful response returns 200 with a top-level app object. It includes the new app ID, stored metadata, creation timestamp, a placement relationship receipt, and a create-only secret_key. Invalid JSON, missing or unknown attributes, unsupported relationship policy values, and unauthorized placement return 422; missing or invalid authentication returns 401.

Optional app attributes are omitted when empty. Although secret_key is expected for normal public creation, clients must still check that it is present before attempting to store the token.

Response attributes

  • Name
    alias
    Type
    string
    Description

    Short label stored for the app.

  • Name
    created_at
    Type
    timestamp
    Description

    When the app was created.

  • Name
    description
    Type
    string
    Description

    Description stored for the app.

  • Name
    id
    Type
    string
    Description

    Unique app ID with the app_ prefix.

  • Name
    name
    Type
    string
    Description

    Display name stored for the app.

  • relationshipobjectReceipt for the parent-child relationship created with the app.Click or tap to expand
    • Name
      actor_app_id
      Type
      string
      Description
      App whose authority initiated creation.
    • Name
      child_app_id
      Type
      string
      Description
      ID of the newly created child app.
    • Name
      child_standing
      Type
      string
      Description
      Standing applied to the child app.
    • Name
      created_at
      Type
      timestamp
      Description
      When the relationship was created.
    • Name
      creator_app_id
      Type
      string
      Description
      App recorded as the creator.
    • Name
      id
      Type
      string
      Description
      Unique identifier for the relationship.
    • Name
      kind
      Type
      string
      Description
      Relationship kind.
    • Name
      placement_parent_app_id
      Type
      string
      Description
      ID of the app under which the child was placed.
    • Name
      policy_version
      Type
      string
      Description
      Version of the applied relationship policy.
    • Name
      relationship_policy
      Type
      object
      View relationship_policy detailsClick or tap to expand
      Applied child_standing, credentials, and management values.
    • Name
      retained_creator_authority_exists
      Type
      boolean
      Description
      Whether the relationship retained creator authority.
    • Name
      status
      Type
      string
      Description
      Current relationship status.
    • Name
      subject_app_id
      Type
      string
      Description
      App governed by the relationship.
  • secret_keyobjectInitial secret key for the new app. Returned only by this endpoint.Click or tap to expand
    • Name
      id
      Type
      string
      Description
      Unique identifier for the secret key.
    • Name
      issued_at
      Type
      timestamp
      Description
      When the secret key was issued.
    • Name
      token
      Type
      string
      Description
      Bearer token value. Store this value immediately; it is returned only once.
    • Name
      token_type
      Type
      string
      Description
      Token type. Currently bearer.

Request

POST/apps/create
curl https://api.inttegro.com/apps/create \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"alias": "acme-prod-api",
"description": "Production Inttegro API for Acme Marketplace",
"legal_entity_type": "business",
"name": "Acme Production API"
}'

Response

SDK versionv8.2.0
AppResponse {
app: {},
}
POST/apps/lookup

Lookup an app

Retrieve the app associated with the API key used on the request. Use this endpoint to confirm which app a secret key authenticates as, or to display app metadata in your own tooling.

The request has no body. An empty JSON object is also accepted. Unknown attributes are rejected. The response includes app metadata only; it never includes secret key values.

Request attributes

No request body is required.

Response shape

The response returns your current app as a top-level app object.

Response attributes

  • Name
    alias
    Type
    string
    Description

    Short label stored for the app.

  • Name
    archived_at
    Type
    timestamp
    Description

    When the app was archived. Omitted while the app is active.

  • Name
    created_at
    Type
    timestamp
    Description

    When the app was created.

  • Name
    description
    Type
    string
    Description

    Description stored for the app.

  • Name
    id
    Type
    string
    Description

    Unique app ID with the app_ prefix.

  • Name
    name
    Type
    string
    Description

    Display name stored for the app.

  • Name
    updated_at
    Type
    timestamp
    Description

    When the app metadata was last updated. Omitted until the first update.

Request

POST/apps/lookup
curl -X POST https://api.inttegro.com/apps/lookup \
-H "Authorization: Bearer $INTTEGRO_API_KEY"

Response

SDK versionv8.2.0
AppResponse {
app: {},
}
POST/apps/update

Update an app

Update metadata for the app associated with the API key used on the request. This endpoint changes app labels and classification; it does not rotate secret keys or move resources between apps.

Send at least one mutable attribute. Unknown attributes are rejected. Text values are trimmed; empty alias, description, and legal_entity_type values clear those fields, while an empty name is rejected. Sending values that are already stored succeeds without changing updated_at.

A successful update returns 200; invalid JSON, an empty update, unknown attributes, or a failed update returns 422, and missing or invalid authentication returns 401.

Request attributes

  • Name
    alias
    Type
    string
    Description

    New short label for the app. Send an empty string to clear it.

  • Name
    description
    Type
    string
    Description

    New app description. Send an empty string to clear it.

  • Name
    name
    Type
    string
    Description

    New display name for the app. Must not be empty after trimming whitespace.

Response shape

The response returns a top-level app object with the current metadata after the update.

Response attributes

  • Name
    alias
    Type
    string
    Description

    Short label stored for the app.

  • Name
    created_at
    Type
    timestamp
    Description

    When the app was created.

  • Name
    description
    Type
    string
    Description

    Description stored for the app.

  • Name
    id
    Type
    string
    Description

    Unique app ID with the app_ prefix.

  • Name
    name
    Type
    string
    Description

    Display name stored for the app.

  • Name
    updated_at
    Type
    timestamp
    Description

    When the app metadata was last updated.

Request

POST/apps/update
curl https://api.inttegro.com/apps/update \
-H "Authorization: Bearer $INTTEGRO_API_KEY" \
-H "Idempotency-Key: app-update-acme-checkout-001" \
-H "Content-Type: application/json" \
-d '{
"alias": "acme-checkout-api",
"description": "Checkout API for Acme Marketplace",
"legal_entity_type": "business",
"name": "Acme Checkout API"
}'

Response

SDK versionv8.2.0
AppResponse {
app: {},
}