Create a payment card with predefined ID in Rebilly

What this operation does

Create a payment card with predefined ID

• PUTChanges data · Payment Cardsapi-sandbox.rebilly.com/payment-cards/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Rebilly operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Rebilly operations

• Create Customer Timeline custom event typePOST · changes data
• Create a filePOST · changes data
• Create an invoicePOST · changes data
• Create a customer (without an ID)POST · changes data
• Create an orderPOST · changes data
• Create an invoice itemPOST · changes data
• Create an invoice Timeline commentPOST · changes data
• Create a customer Timeline comment or custom defined eventPOST · changes data

All 184 Rebilly operations

Questions

Can HumDay create a payment card with predefined id in Rebilly?

Yes. This operation is published in Rebilly's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Rebilly data?

Yes — this is a PUT operation, so it changes something in Rebilly. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Rebilly account.

Where this came from

Read from a published API description for Rebilly at api-reference.rebilly.com/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-06-07.