PASAR API
Use API v6 for current Account Information and Payment Initiation integrations. Requests use App-id and Secret headers; live clients must use request signing. v6 requires service API keys and a widget flow rather than the former Direct API or app API keys. Check bank coverage and enterprise terms with Salt Edge.
View docs ↗ More Banking & finance APIs All Malaysia APIs Alternatives to Salt Edge# Use the provider's documented signing flow or SDK; a generic bearer header is not sufficient. # https://docs.saltedge.com/
I'm integrating a Malaysia API into my app. API: Salt Edge Open Banking Aggregator Provider: Salt Edge Auth: requires an access token (sign up: https://docs.saltedge.com/) Pricing: paid Base URL: https://www.saltedge.com/api/v6 Important note: Use API v6 for current Account Information and Payment Initiation integrations. Requests use App-id and Secret headers; live clients must use request signing. v6 requires service API keys and a widget flow rather than the former Direct API or app API keys. Check bank coverage and enterprise terms with Salt Edge. Source: Salt Edge (https://docs.saltedge.com/) Source type: Provider API or developer docs Endpoint type: Provider API base URL Integration difficulty: Needs token Last checked: 2026-06-15 Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs. Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.