---
title: "API keys and integrations - NexPay"
description: "Create and manage API keys to connect NexPay to your own systems, plus the no-code and developer options — Zapier and the REST API."
lastModified: "2026-06-02"
lang: "en"
url: https://nexpay.com.au/training/team-and-account/api-keys-and-integrations
---
## Site navigation

- For businesses
  - [For ed. agents](/for-education-agents.md)
  - [For schools & colleges](/for-schools.md)
  - [For universities](/for-universities.md)
  - [For accommodation](/for-accommodation.md)
  - [Why NexPay?](/about.md)
  - [Pricing](/pricing.md)
  - [AI automation](/payments-ai-automation.md)
- [For students & parents](/for-students-and-parents.md)
- Help & resources
  - [Training](/training.md)
  - [Blog](/blog.md)
  - [Events](/events.md)
  - [Zapier integration](/zapier.md)
  - [Claude & ChatGPT](/mcp.md) — Claude & ChatGPT integration
- [Contact](/contact-us.md)
- [Login](https://portal.nexpay.com.au/login)

# API keys and integrations - NexPay

## At a glance

- **Intended for:** Admins & developers
- **Reading time:** 5 minutes
- **Last updated:** 1st June 2026

**TL;DR:** API keys let you connect NexPay to other systems. Create one in Settings → API Keys with a label; NexPay shows the Client ID and Secret once, so copy the secret immediately and store it safely. Revoke a key any time to cut off its access. For no-code automation there's Zapier; for developers there's a full REST API. Keys are the credentials behind both custom and developer integrations.

{/* Body content for API keys & integrations */}

## Connecting NexPay to the rest of your stack

NexPay doesn't have to be an island. If you run your own student portal, CRM, or accounting system, you can connect it to NexPay so payments and data flow between them. The credential that makes those connections work is an **API key**. This article covers creating and managing keys, plus the two main ways to integrate — no-code via Zapier, and a full REST API for developers.

If you're not building an integration, you can safely skip this one — it's here for when you are.

> **For admins and developers:** Treat API keys like passwords. The few habits below — clear labels, copying the secret immediately, revoking unused keys — keep your integrations both working and secure.

## Creating an API key

API keys live in **Settings → API Keys**. To create one:

1. Choose **Create key**.
2. Give it a clear **label** — something like "Mobile App" or "Accounting sync" — so you'll recognise what it's for later.
3. NexPay shows you a **Client ID** and a **Secret**.

The Client ID identifies the key; the Secret is the sensitive half that authenticates it.

> **Important:** The **Secret is shown only once**, right after you create the key. Copy it immediately and store it somewhere safe (a password manager or your system's secret store). If you navigate away without copying it, there's no way to see it again — you'd have to revoke the key and create a new one. This one-time reveal is a security feature, so treat that moment with care.

## Managing your keys

The API Keys tab lists your keys, each showing its label, a shortened Client ID you can copy, when it was created, and when it was last used. This makes it easy to see at a glance which keys are active and which have gone quiet.

When a key is no longer needed — or if you suspect it's been exposed — **Revoke** it. Revoking immediately stops that key from working. Revoked keys remain visible (in a separate, greyed-out section) for your records, but they can't be used again.

> **Quick tip:** Give every key a purpose-specific label and revoke ones you've stopped using. A tidy key list means that if you ever need to cut off one integration, you can do it precisely without disrupting the others.

## No-code automation with Zapier

You don't have to write code to connect NexPay to your tools. NexPay integrates with **Zapier**, which lets you build automations without programming — for example, triggering a payment from your CRM, syncing new NexPay payments to a spreadsheet or your accounting system, or posting a notification to your team chat.

It's the right starting point for most teams who want to automate a workflow but don't have engineering time to spare. Learn what's possible on the [Zapier integration page](/zapier.md).

## The REST API for developers

For deeper or fully custom integrations, NexPay offers a complete **REST API**. It gives programmatic access to payments, students, payees, and payers, with authentication, webhooks, a sandbox mode for safe testing, and an OpenAPI specification. This is the route when you're building something bespoke — your own portal creating payments directly, say.

Your API keys are the credentials your code uses to authenticate against it. The full technical reference lives on the [API documentation page](/api.md), and there's deeper developer documentation linked from your dashboard.

## Your next step

- **Want no-code automation?** Explore the [Zapier integration](/zapier.md).
- **Building a custom integration?** See the [REST API documentation](/api.md).
- **Managing who can access settings?** Read [managing your team](/training/team-and-account/managing-your-team.md).
- **Setting up the organisation?** See [profile and organisation settings](/training/team-and-account/profile-and-organisation-settings.md).

## Checkpoint

After reading this, you should be able to:

- Explain what an API key is and when you'd need one
- Create a key with a clear label and copy the secret immediately
- Revoke a key to cut off its access, and find your revoked keys
- Choose between Zapier (no-code) and the REST API (developer) for integrating
- Apply good key hygiene — clear labels, safe storage, revoking unused keys

## Frequently asked questions

### What's an API key for?

It's a credential that lets another system connect to NexPay on your behalf — for example, your own portal creating payments programmatically, or a tool reading your payments. If you're not building an integration, you don't need one.

### How do I create an API key?

In Settings, open the API Keys tab and choose Create key. Give it a clear label (like "Mobile App" or "Accounting sync") so you'll recognise it later. NexPay then shows you the Client ID and a Secret.

### I didn't copy the secret. Can I see it again?

No — the secret is shown only once, at creation, for security. If you've lost it, the safe path is to revoke that key and create a new one, then update wherever the credential was used. That's why it's important to copy and store the secret as soon as it appears.

### How do I stop a key from working?

Revoke it. On the API Keys tab, each active key has a Revoke option. Revoking immediately cuts off that key's access — useful if a key is no longer needed or you suspect it's been exposed. Revoked keys are kept visible for your records but can't be used.

### Do I need to write code to integrate with NexPay?

Not necessarily. For no-code automation, NexPay connects to Zapier so you can trigger payments and sync data without writing anything. For deeper or custom integrations, there's a full REST API for developers. API keys are the credentials for both.

### Who should manage API keys?

Treat them like passwords — limit who creates and holds them, give each a clear label, and revoke ones you no longer use. They grant programmatic access to your account, so they deserve the same care as any sensitive credential.

### Is there a sandbox, and are there webhooks?

Yes to both. Integrations start in a sandbox where you can simulate payments and test webhooks with realistic data before going live, and webhooks notify your system of events like payment status changes. Authentication uses a Bearer token. The exact endpoints, event types, and setup live in the API reference — your engineers should start there.

### What about rate limits, idempotency, scopes, and versioning?

These are real concerns for a production integration, and the specifics — request limits, how to retry safely without duplicating a payment, what a key can access, and how changes are versioned — are documented in the API reference rather than here. This training article is the on-ramp; the API reference is the source of truth for those details. If your team needs something that isn't covered, NexPay's engineers can help during onboarding.

## More on NexPay

**Platform**

- [For students & parents](/for-students-and-parents.md)
- [For ed. agents](/for-education-agents.md)
- [For universities](/for-universities.md)
- [For schools](/for-schools.md)
- [For accommodation](/for-accommodation.md)
- [AI automation](/payments-ai-automation.md)
- [Pricing](/pricing.md)

**Help & resources**

- [Training](/training.md)
- [Contact](/contact-us.md)
- [Developers](/api.md)
- [Zapier integration](/zapier.md)
- [Claude & ChatGPT](/mcp.md) — Claude & ChatGPT integration

**Company**

- [About](/about.md) — About NexPay
- [Jobs](/about.md#jobs)
- [Blog](/blog.md)
- [Media](/media.md)
- [Events](/events.md)

**Trust & locations**

- [Trust & Regulatory](/trust.md)
- [Our offices](/locations.md)

**Legal**

- [Terms and Conditions](/terms-and-conditions/)
- [Privacy policy](/privacy-policy/)
- [Cookie Policy](/cookie-policy/)
- [Complaints Policy](/complaints-policy/)
- [Financial Services Guide](/financial-services-guide/)
- [Product Disclosure Statement](/product-disclosure-statement/)
- [AML Policy](/aml-policy/)
- [Target Market Determination](/target-market-determination/)
- [Group Regulatory Disclosure](/group-regulatory-disclosure/)
- [Fees & FX Schedule](/fees-and-fx/)
- [Developer & API Terms](/developer-terms/)

## NexPay

NexPay Pty Ltd (ABN 56 153 910 984) holds Australian Financial Services Licence No. 560782 and is authorised to provide non-cash payment services to retail and wholesale clients in Australia.

- **Address:** Level 12, 64 York St, Sydney NSW 2000, Australia
- **Support:** [support@nexpay.com.au](mailto:support@nexpay.com.au)
- **Status:** [https://nexpay1.statuspage.io/](https://nexpay1.statuspage.io/)

**Follow NexPay**

- [LinkedIn](https://au.linkedin.com/company/nexpay)
- [Instagram](https://www.instagram.com/nexpayau/)
- [Facebook](https://www.facebook.com/NexPayAU)

© NexPay Pty Ltd