---
title: "Create AS2 Partner"
method: POST
path: "/as2_partners"
tags: ["as2_partners", "AS2 Partners"]
---

# Create AS2 Partner

`POST /as2_partners`

Create AS2 Partner

## Response `201`

The As2Partners object.

- As2PartnerEntity — As2PartnerEntity model
  - `id` integer — ID of the AS2 Partner.
  - `workspace_id` integer — ID of the Workspace associated with this AS2 Partner.
  - `as2_station_id` integer — ID of the AS2 Station associated with this partner.
  - `name` string — The partner's formal AS2 name.
  - `uri` string — Public URI where we will send the AS2 messages (via HTTP/HTTPS).
  - `server_certificate` 'require_match' | 'allow_any' — Should we require that the remote HTTP server have a valid SSL Certificate for HTTPS? (This only applies to Outgoing AS2 message from Files.com to a Partner.)
  - `http_auth_username` string — Username to send to server for HTTP Authentication.
  - `additional_http_headers` object — Additional HTTP Headers for outgoing message sent to this partner.
  - `default_mime_type` string — Default mime type of the file attached to the encrypted message
  - `mdn_validation_level` 'none' | 'weak' | 'normal' | 'strict' | 'auto' — How should Files.com evaluate message transfer success based on a partner's MDN response? This setting does not affect MDN storage; all MDNs received from a partner are always stored. `none`: MDN is stored for informational purposes only, a successful HTTPS transfer is a successful AS2 transfer. `weak`: Inspect the MDN for MIC and Disposition only. `normal`: `weak` plus validate MDN signature matches body, `strict`: `normal` but do not allow signatures from self-signed or incorrectly purposed certificates. `auto`: Automatically set the correct value for this setting based on next mdn received.
  - `signature_validation_level` 'normal' | 'none' | 'auto' — Should Files.com require signatures on incoming AS2 messages? `normal`: require that incoming messages are signed with a valid matching signature. `none`: Unsigned incoming messages are allowed. `auto`: Automatically set the correct value for this setting based on next message received.
  - `enable_dedicated_ips` boolean — If `true`, we will use your site's dedicated IPs for all outbound connections to this AS2 Partner.
  - `hex_public_certificate_serial` string — Serial of public certificate used for message security in hex format.
  - `public_certificate` string — Public certificate used for message security.
  - `public_certificate_md5` string — MD5 hash of public certificate used for message security.
  - `public_certificate_subject` string — Subject of public certificate used for message security.
  - `public_certificate_issuer` string — Issuer of public certificate used for message security.
  - `public_certificate_serial` string — Serial of public certificate used for message security.
  - `public_certificate_not_before` string — Not before value of public certificate used for message security.
  - `public_certificate_not_after` string — Not after value of public certificate used for message security.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not Found
- `405` — Method Not Allowed
- `409` — Conflict
- `412` — Precondition Failed
- `422` — Unprocessable Entity
- `423` — Locked
- `429` — Too Many Requests

---

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