Skip to main content
DELETE

File Transfer Tokenization Guide

Tokenize card data in files on sFTP and FTPS servers
Deletes a file on a third party’s sFTP or FTPS server, with PCI Booking connecting to the server for you. A typical use is right after Tokenize from sFTP: PCI Booking has tokenized the file, but the original file with the real card data is still on the server. Deleting it through PCI Booking removes it without your own systems connecting to the server or handling the card data. Use /api/sftp/ for an sFTP server and /api/ftps/ for an FTPS server. FTPS connections use explicit TLS; implicit TLS (port 990) is not supported.

Error Responses

Parameter Constraints

  • serverAddress: hostname or hostname:port. Only one colon is allowed. Without a port, PCI Booking connects on port 22. Most FTPS servers listen on port 21, so for FTPS you will usually add :21.
  • Authorization header: Basic credentials (username:password) for the remote server.

Parameters

Authentication

This is a browser-facing endpoint. Use one of the authentication methods below instead of the API key shown above.
string
Recommended. A long-lived token for browser-side calls. How to generate.
string
Alternative. Valid for 5 minutes. How to generate.
If both are provided, the session token takes precedence.

Path Parameters

string
required
The server address: an IP address or domain name, optionally followed by a colon and the port. For example: sftp.gateway.com or ftps.gateway.com:21.
string
required
The path of the file to delete on the server, including folders and the file name. For example: outgoing/reservations/2026-09-25.xml.

Headers

string
required
Basic credentials for the remote server, in the form Basic base64(username:password). These are the credentials of the sFTP or FTPS server, not your PCI Booking credentials.

Response

204 - The file was deleted. There is no response body. This call is not billed.