> ## Documentation Index > Fetch the complete documentation index at: https://developer.hellgate.io/llms.txt > Use this file to discover all available pages before exploring further. # Upload a certificate > Return the signed certificate chain Apple issued for a CSR created with [Create Apple Pay certificates](/products/guardian/api-reference/wallet/create-certificates). Once uploaded, the certificate moves to `active` and becomes the one Guardian uses to decrypt payloads and authenticate to Apple. ## OpenAPI ````yaml /products/guardian/openapi.yaml post /api/wallet/apple-pay/certificates/{id}/upload openapi: 3.1.0 info: title: Guardian API version: '1.0' contact: name: Starfish GmbH & Co. KG email: support@hellgate.io url: https://hellgate.io/cpa/guardian license: name: Hellgate API Terms url: https://hellgate.io/terms-and-conditions servers: - url: https://{instance}.{env}.on-hellgate.cloud description: Managed instance of Guardian variables: instance: default: my-instance description: Your unique instance slug, provided during onboarding. env: default: eu1 description: Deployment environment (currently eu1). security: [] tags: - name: pci description: Management of card payment credentials under the ruling of PCI DSS. - name: network description: Management of network tokens and cryptograms for secure transactions. - name: generic description: Management of generic tokens and their schemas for various use cases. - name: metadata description: Inquiries for card metadata based on PAN, PCI tokens, or network tokens. - name: wallet description: >- Management of wallet tokens ingested from device wallets such as Google Pay. - name: apikey description: Management of API keys for service access. - name: webhook description: Management of webhooks for event notifications. - name: types description: Management of types for generic token schemas. paths: /api/wallet/apple-pay/certificates/{id}/upload: post: tags: - wallet summary: Upload a certificate description: > Return the signed certificate chain Apple issued for a CSR created with [Create Apple Pay certificates](/products/guardian/api-reference/wallet/create-certificates). Once uploaded, the certificate moves to `active` and becomes the one Guardian uses to decrypt payloads and authenticate to Apple. operationId: wallet_apple_pay_certificate_upload parameters: - in: path name: id description: The ID of the certificate the CSR was issued for. required: true schema: type: string format: uuid requestBody: content: application/json: schema: $ref: '#/components/schemas/apple_pay_certificate_upload_request' responses: '200': description: Success response content: application/json: schema: $ref: '#/components/schemas/apple_pay_certificate' '401': $ref: '#/components/responses/401_UnauthorizedError' '403': $ref: '#/components/responses/403_ForbiddenError' '404': $ref: '#/components/responses/404_NotFoundError' '409': $ref: '#/components/responses/409_ConflictError' '422': $ref: '#/components/responses/422_ValidationError' security: - bearerAuth: [] - APIKey: [] components: schemas: apple_pay_certificate_upload_request: type: object properties: signed_cert_chain: example: |- -----BEGIN CERTIFICATE----- MIIEhTCCBCugAwIBAgII... -----END CERTIFICATE----- type: string description: PEM-encoded signed certificate chain from Apple. required: - signed_cert_chain apple_pay_certificate: title: Apple Pay Certificate type: object properties: id: example: 4f8a2c6e-3b9d-4a1f-8e7c-5d2b9f4a6e8c type: string format: uuid state: type: string example: active enum: - pending - active - retired - disabled registration_order: example: 1 type: integer expires_at: example: '2028-02-01T09:00:00Z' type: string format: date-time nullable: true activated_at: example: '2026-02-03T10:00:00Z' type: string format: date-time nullable: true retired_at: example: null type: string format: date-time nullable: true disabled_at: example: null type: string format: date-time nullable: true created_at: example: '2026-02-01T09:10:00Z' type: string format: date-time required: - id - state - registration_order - created_at ErrorGeneric: type: object properties: code: $ref: '#/components/schemas/ErrorStatusCode' classifier: $ref: '#/components/schemas/ErrorClassifier' message: $ref: '#/components/schemas/ErrorMessage' ErrorValidation: type: object properties: code: $ref: '#/components/schemas/ErrorStatusCode' classifier: $ref: '#/components/schemas/ErrorClassifier' message: $ref: '#/components/schemas/ErrorMessage' validation_errors: type: array items: type: object properties: path: example: $.source.account_number type: string description: Json-path in the request which points to the validation error message: example: is required type: string description: Human readable validation message ErrorStatusCode: type: integer description: The corresponding HTTP status code for the error ErrorClassifier: type: string description: Technical code that helps to identify the error ErrorMessage: type: string description: Human readable representation of the error responses: 401_UnauthorizedError: description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 401 message: No valid means of authentication was provided classifier: UNAUTHORIZED 403_ForbiddenError: description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 403 message: Not allowed to access this resource or feature classifier: FORBIDDEN 404_NotFoundError: description: Not found content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 404 message: The requested resource was not found. classifier: NOT_FOUND 409_ConflictError: description: Conflict content: application/json: schema: $ref: '#/components/schemas/ErrorGeneric' example: code: 409 message: Conflict classifier: CONFLICT 422_ValidationError: description: Validation error content: application/json: schema: $ref: '#/components/schemas/ErrorValidation' example: code: 422 classifier: VALIDATION_ERROR message: Validation error validation_errors: - path: json-path message: human readable error message securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- JWT bearer token obtained via the OAuth2 client-credentials grant from the platform Authentication API. The token's scopes gate the endpoints it may call, and its audience names the Guardian instance. This is the standard way to authenticate to Guardian. APIKey: type: apiKey name: x-api-key in: header description: >- Deprecated. Long-lived instance API key, sent as `x-api-key`. Existing integrations continue to work, but new ones should use the OAuth2 bearer token instead. ````