Get a subscription's current prepaid settings in SIGNL4

What this operation does

Get a subscription's current prepaid settings.

• GETReads data · Prepaidconnect.signl4.com/subscriptions/{subscriptionId}/prepaidSettings

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 SIGNL4 operations the program may use, and this is one of them.
3. You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.

Other SIGNL4 operations

• Create WebhookPOST · changes data
• Get overview event pagedPOST · changes data
• Creates a new script instance in the in the SIGNL4 teamPOST · changes data
• Create a new categoryPOST · changes data
• Sends invite email again if an invite existsPOST · changes data
• Uploaded a profile image for a specified userPOST · changes data
• Updates user profile of an userPUT · changes data
• Punch User inPOST · changes data

All 101 SIGNL4 operations

Questions

Can HumDay get a subscription's current prepaid settings in SIGNL4?

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

Does this change anything in my SIGNL4 account?

No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in SIGNL4.

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 SIGNL4 account.

Where this came from

Read from a published API description for SIGNL4 at connect.signl4.com/api/docs/v1/swagger.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.