Welcome to Pliant's Pro API

Everything you need to integrate Pliant's corporate card management into your systems. Issue cards, track spending, and manage expenses—all through our API.

What can you do with this API?

Issue virtual and physical cards for your team
Set spending limits per card, per employee, or per department
Track transactions in real-time
Automate expense management with your existing accounting tools
Control card access — freeze, unfreeze, or cancel cards instantly

Getting Started (3 steps)

STEP 1

Get your API credentials

Contact your Pliant account manager to receive your API key and secret.

STEP 2

Authenticate your requests

Use your credentials to generate access tokens. See "Authentication and Authorisation" below.

STEP 3

Make your first API call

Start with the Test Data section to safely experiment before going live.

Documentation

📘 Basics

New to the API? Start here.

Getting Started
Core Concepts
Business Entities

⚙️ API Fundamentals

How the API works under the hood.

API Guidelines
API Lifecycle and Versioning
Pagination & Ordering

🔐 Authentication and Authorisation

Secure your API requests.

Authenticated API Usage
Authenticated Callbacks

🚀 Features & Use Cases

Real-world integration examples.

Quick Start for Travel API Consumers
Quick Start for Accounting API Consumers
Card Controls

🔒 Sensitive Card Data (PCI)

Handling card numbers and CVVs securely.

PCI API
PCI Proxy API
PCI Widget Web

🧪 Test Data

Try the API without affecting real data.

Generate Test Data

Need help?

Check the Discussions tab for community Q&A, or contact Support for direct assistance.

200Ok

400Bad Request. The API consumer sent a malformed request which could not be processed.

401Unauthorized. The API consumer is not authorized to access the requested resource.

403Forbidden. The API consumer is not allowed to access the requested resource.

429Too Many Requests. The API consumer has sent too many requests in a given amount of time. Please check our API guidelines.

500Internal Server Error. The request was not completed due to an internal error.