Changelog

Version	Date	Description	Created by
1.0	2025-05-20	Created document	Anders Göthberg
1.1		API in production	Anders Göthberg

Introduction

Link to the general step-by-step implementations guide that guides you through setting up a REST API integration towards PayEx Invoice Service can be found here 

The Billing Customer API is used to create and update the company's end customers' billable charges at both the customer and each subscription level.

Customer API

Route description

Each resource in the API corresponds to its own route. All routes are structured according to a specific standard, explained below

The below route is an example of a route towards resource3Id, to operate on this resource you must also include the ids of its parent resources in the route.
lf-api.payex.com/billing/{subdomain}/v1/{ownerNo}/resource1/{resource1Id}/resource2/{resource2Id}/resource3/{resource3Id}

Route segment	Description
subdomain	In this part of the API it will be "billing"
ownerNo	The ledger identifier/number at PayEx
resource1Id	Identifier of resource1 (customers)
resource2Id	identifier of resource2, subresource to resource1 (recurring products or subscriptions)
resource3Id	identifier of resource3, subresource to resource2 (recurring products)

Routes that occurs in examples of this documentation will use the following identifiers

Resource	Identifier
ownerNo	The ledger identifier/number at PayEx
customerNo	Customer number
subscriptionNo	Subscription number (identifier for subscription)
recurring-products	Recurring products on customer or subscription level

Swaggerfil!!!

Problem types

Problem type (code)	Http status	Description
validation	400	occurs if any of the inputvalidation fails, it is described in the problem which parameter that failed the validation
customer-not-found	404	Customer not found in PayEx Billing
subscription-not-found	404	Subscription not found on selected customer