Can HumDay connect to Openbankingproject Swiss NextGen Banking Framework?

Yes. HumDay reads Openbankingproject Swiss NextGen Banking Framework's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 34 operations are documented.

Do I need to write code to automate Openbankingproject Swiss NextGen Banking Framework?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Openbankingproject Swiss NextGen Banking Framework account.

What can HumDay do in Openbankingproject Swiss NextGen Banking Framework?

15 of the 34 documented operations change something in Openbankingproject Swiss NextGen Banking Framework, and 19 read from it. HumDay only ever uses the specific operations your approved contract needs.

Automate Openbankingproject Swiss NextGen Banking Framework

HumDay reads Openbankingproject Swiss NextGen Banking Framework’s own published API description and derives 34 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Openbankingproject Swiss NextGen Banking Framework is

# Summary The **Swiss NextGen API** is based on the NextGenPSD2 *Framework Version 1.3.4* of the Berlin Group which offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGen Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe

API host: api.dev.openbankingproject.ch

What HumDay can do in Openbankingproject Swiss NextGen Banking Framework

15 documented operations change something in Openbankingproject Swiss NextGen Banking Framework.

POSTCreate consent/v1/consents
POSTCreate a signing basket resource/v1/signing-baskets
POSTConfirmation of funds request/v1/funds-confirmations
POSTPayment initiation request/v1/{payment-service}/{payment-product}
DELETEDelete Consent/v1/consents/{consentId}
DELETEDelete the signing basket/v1/signing-baskets/{basketId}
DELETEPayment cancellation request/v1/{payment-service}/{payment-product}/{paymentId}
POSTStart the authorisation process for a consent/v1/consents/{consentId}/authorisations
POSTStart the authorisation process for a signing basket/v1/signing-baskets/{basketId}/authorisations
POSTStart the authorisation process for a payment initiation/v1/{payment-service}/{payment-product}/{paymentId}/authorisations
POSTStart the authorisation process for the cancellation of the addressed payment/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations
PUTUpdate PSU Data for consents/v1/consents/{consentId}/authorisations/{authorisationId}
PUTUpdate PSU data for signing basket/v1/signing-baskets/{basketId}/authorisations/{authorisationId}
PUTUpdate PSU data for payment initiation/v1/{payment-service}/{payment-product}/{paymentId}/authorisations/{authorisationId}
PUTUpdate PSU data for payment initiation cancellation/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations/{authorisationId}

What HumDay can read from Openbankingproject Swiss NextGen Banking Framework

These are the operations a schedule or a trigger can watch.

GETRead account list/v1/accounts
GETRead transaction list of an account/v1/accounts/{account-id}/transactions
GETGet consent request/v1/consents/{consentId}
GETRead account details/v1/accounts/{account-id}
GETReturns the content of an signing basket object/v1/signing-baskets/{basketId}
GETGet payment information/v1/{payment-service}/{payment-product}/{paymentId}
GETConsent status request/v1/consents/{consentId}/status
GETRead balance/v1/accounts/{account-id}/balances
GETRead the status of the signing basket/v1/signing-baskets/{basketId}/status
GETGet consent authorisation sub-resources request/v1/consents/{consentId}/authorisations
GETGet signing basket authorisation sub-resources request/v1/signing-baskets/{basketId}/authorisations
GETPayment initiation status request/v1/{payment-service}/{payment-product}/{paymentId}/status
GETGet payment initiation authorisation sub-resources request/v1/{payment-service}/{payment-product}/{paymentId}/authorisations
GETWill deliver an array of resource identifications to all generated cancellation authorisation sub-resources/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations
GETRead transaction details/v1/accounts/{account-id}/transactions/{transactionId}
GETRead the SCA status of the consent authorisation/v1/consents/{consentId}/authorisations/{authorisationId}
GETRead the SCA status of the signing basket authorisation/v1/signing-baskets/{basketId}/authorisations/{authorisationId}
GETRead the SCA status of the payment authorisation/v1/{payment-service}/{payment-product}/{paymentId}/authorisations/{authorisationId}
GETRead the SCA status of the payment cancellation's authorisation/v1/{payment-service}/{payment-product}/{paymentId}/cancellation-authorisations/{authorisationId}

How automating Openbankingproject Swiss NextGen Banking Framework works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Openbankingproject Swiss NextGen Banking Framework account.
Grant access, then go live. You approve the specific Openbankingproject Swiss NextGen Banking Framework operations it may use — and only those.