---
title: "Create New Gateway Endpoint Configuration"
method: POST
path: "/ach/gateways"
tags: ["ACH"]
---

# Create New Gateway Endpoint Configuration

`POST /ach/gateways`

By creating Gateway Endpoint Configuration object for Fintech,
you enable ACH in Auth flow for all the ACH transactions for specified Fintech (Tenant)

## Request body

- GatewayPost — Gateway Config Create Request
  - `custom_headers` object — Optional parameter that allows to configure custom http headers for the Auth request to Gateway URL if needed
  - `disabled` boolean — Setting this parameter to 'true' allows create Gateway Config as inactive ( can be useful as a preparation step)
  - `max_wait_ms` integer — Optional parameter that configures the maximum amount of time in milliseconds that we will wait for the response from Gateway URL request. Default value is used if empty
  - `url` string, url, required — The URL address which will be used for the ACH in Auth Flow requests to get authorization from the fintech to process the transaction

## Response `201`

Created Gateway Config Object

- GatewayConfig — Represents a Gateway Config Object
  - `created` string, date-time — Time when Gateway Config object was created
  - `custom_headers` object — Optional parameter that allows to configure custom http headers for the Auth request to Gateway URL if needed
  - `disabled` boolean — Indicates if the Gateway Config is active for Auth Flow for the current Fintech (Tenant)
  - `id` string, uuid — Identifier of the Gateway Config object
  - `max_wait_ms` integer — Shows maximum amount of time in milliseconds that we will wait for the response from Gateway URL Auth request
  - `tenant` string, required — The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.
  - `updated` string, date-time — Time when Gateway Config object was updated
  - `url` string, url — The URL address which will be used for the ACH in Auth Flow requests to get authorization from the fintech to process the transaction

## Other responses

- `400` — BadRequest
- `403` — Forbidden error
- `500` — Internal server error

---

[API](https://skmtc.net/synctera/apis/synctera-api.md) · [All operations](https://skmtc.net/synctera/apis/synctera-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/synctera/synctera-api/revisions/b0d812e6cdd0/schema)