> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # Request Travel Rule Network Access API > Ask Didit to carry your application on GTR or Sygna as its own participant, after your questionnaire is approved. Request a Travel Rule Network API Prompt Copy prompt to clipboard 
  \`Ask Didit to carry my application on a Travel Rule network as my own participant.

  Endpoint:
  POST [https://verification.didit.me/v3/travel-rule/networks/\{network}/request/](https://verification.didit.me/v3/travel-rule/networks/\{network}/request/)
  network: gtr | sygna

  Authentication:
  Use the x-api-key header with my Didit API key. No request body.

  Behavior:

  * Without an approved questionnaire, the participant waits for it (status questionnaire\_pending).
  * With one, it goes to the network's onboarding (submitted\_to\_network) and becomes active once the network gives it a participant code.
  * Idempotent: a pending, onboarding or active participant is returned unchanged.
  * If the network refused the registration (last\_error is set and the network's state is error / provisioning\_failed), requesting again retries.
  * 400 travel\_rule\_network\_own\_membership\_only for TRUST and VerifyVASP (connect your own membership instead), 400 travel\_rule\_network\_sandbox\_application from a sandbox application, 403 travel\_rule\_platform\_networks\_disabled until network access through Didit opens.

  What to read from the response:

  * status, participant\_code, last\_error and history of my participant.

  Full guide: /transaction-monitoring/travel-rule.\`
Paste into Read the result on [Get Travel Rule Networks](https://docs.didit.me/management-api/travel-rule/get-networks.md): the network's `state` becomes `live_through_didit` once your participant is active and Didit's membership of that network is live. ## OpenAPI ````yaml POST /v3/travel-rule/networks/{network}/request/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: Identity verification API. Authenticate with x-api-key header. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/travel-rule/networks/{network}/request/: post: tags: - Travel Rule summary: Request a Travel Rule network description: >- Ask for this application's own participant on a network Didit's membership carries (GTR or Sygna). Without an approved questionnaire the participant waits for it (questionnaire_pending); with one it goes to the network's onboarding (submitted_to_network) and becomes active once the network gives it a code. Idempotent: a pending, onboarding or live participant is returned unchanged. If the network refused the registration (last_error is set), requesting again retries. TRUST and VerifyVASP are reachable only through your own membership: TRUST admits members per VASP, and a VerifyVASP Enclave serves one VASP id. operationId: requestTravelRuleNetworkAccess parameters: - name: network in: path required: true schema: type: string enum: - gtr - sygna description: The network to join through Didit's membership. responses: '200': description: Your participant on the network. content: application/json: schema: $ref: '#/components/schemas/TravelRuleNetworkParticipant' '400': description: >- Unknown network, a network Didit does not carry (connect your own membership), or a sandbox application. content: application/json: schema: type: object properties: detail: type: string code: type: string enum: - travel_rule_network_own_membership_only - travel_rule_network_sandbox_application '401': description: Missing or invalid API key. '403': description: Network access through Didit's membership is not open yet. content: application/json: schema: type: object properties: detail: type: string code: type: string enum: - travel_rule_platform_networks_disabled security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X POST https://verification.didit.me/v3/travel-rule/networks/gtr/request/ \ -H 'x-api-key: YOUR_API_KEY' components: schemas: TravelRuleNetworkParticipant: type: object description: This application's own participant on one network. properties: network: type: string enum: - gtr - trust - verifyvasp - sygna rail: type: string enum: - GTR - TRUST - VERIFYVASP - SYGNA mode: type: string enum: - platform - own status: type: string enum: - not_requested - questionnaire_pending - submitted_to_network - active - suspended - rejected description: >- not_requested: never requested, or the network refused the first request (see last_error); questionnaire_pending: waiting for the due-diligence questionnaire to be approved; submitted_to_network: handed to the network's onboarding; active: the network gave this application its own participant code; suspended / rejected: Didit suspended or rejected it. participant_code: type: string requested_at: type: string format: date-time nullable: true submitted_at: type: string format: date-time nullable: true activated_at: type: string format: date-time nullable: true suspended_at: type: string format: date-time nullable: true last_error: type: string description: >- The network's answer when it refused the registration; empty otherwise. history: type: array readOnly: true description: Every status change, oldest first. items: type: object properties: at: type: string format: date-time from: type: string to: type: string note: type: string description: Review note or the network's answer, when there is one. securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is missing, wrong, revoked or expired; 403 means the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.