> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eazecustoms.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Let's get started

> Implementation instructions for Eaze Customs.

## What you need

* Business information for onboarding setup

## What we provide

* API key and Company ID (issued after onboarding approval)
* Sandbox environment access for testing before production
* Shipment data, document files, or an API workflow for creating declarations

## Integration steps

<Steps>
  <Step title="Complete onboarding">
    Provide your business details to activate your Eaze Customs account:

    **Company Details:** Company name, EORI Number, VAT Number, IOSS Number, Procedure Types (import, export, transit)

    **Contact Person:** First name, Last name, Email, Phone number

    **Address:** House number, Street, City, State/Region, Country code, Postal code
  </Step>

  <Step title="Receive API credentials">
    After approval, you receive an **API key**, **Company ID**, and **Sandbox URL**.
    Store them securely — never commit credentials to version control.
  </Step>

  <Step title="Set up authentication">
    Include your API key as a Bearer credential on every request:

    ```bash theme={null}
    curl -X GET https://devapi.eazecustoms.com/staging/v1/declarations \
      -H "Authorization: Bearer your_api_key_here"
    ```

    See the [Authentication Guide](/implementation/authentication) for environment variables, key rotation, and troubleshooting.
  </Step>

  <Step title="Create declarations">
    Create declarations from your platform with the external API, or let users upload invoices, packing lists, and manifests for OCR-based declaration creation.
    Eaze Customs validates the data and returns a `declaration_id` with the initial status.
    See [Import Declarations](/api-reference/import/submit-declaration), [Export Declarations](/api-reference/export/submit-declaration), [Transit Departure](/api-reference/transit/submit-departure), and [Transit Arrival](/api-reference/transit/submit-arrival).
  </Step>

  <Step title="Review and correct">
    Use validation results to correct missing or invalid declaration data before sending it to customs.
    If customs rules and shipment status allow changes after submission, submit an amendment or request invalidation.
    Every change is recorded in the audit trail.
  </Step>

  <Step title="Track status">
    Poll the status endpoint or configure webhooks to receive `declaration.cleared` and `declaration.rejected` events without polling.
  </Step>

  <Step title="Move to production">
    Once sandbox testing passes, request production credentials and switch the endpoint URL and key in your platform.
  </Step>
</Steps>

For sandbox credentials and support, contact our support team at [support@eazecustoms.com](mailto:support@eazecustoms.com)