Softwr

APIs · head to head

AWS API Gateway vs Salt Edge

AWS API Gateway logo

AWS API Gateway

APIs

Fully managed API gateway service for creating and managing APIs at scale

From
Free
Rated
-
Salt Edge logo

Salt Edge

APIs

Independent open banking aggregator covering Europe by PSD2 API and other markets by direct connection

From
On request
Rated
-

The short version

  • Only AWS API Gateway has a free tier, so it costs nothing to try first.
  • Each has a real cost: AWS API Gateway rEST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer; Salt Edge coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
  • They diverge on capability: AWS API Gateway covers REST APIs, Salt Edge covers Account information.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which AWS API Gateway and Salt Edge actually diverge.

Attributes where AWS API Gateway and Salt Edge differ
AttributeAWS API GatewaySalt Edge
Starting priceFreeOn request
Pricing modelusage-basedquote
Free tierYesNo
PlatformsAWS CloudWeb, API
Founded2006Unknown

Identical on both: user rating (Not yet rated), category (APIs).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in AWS API Gateway

  • REST APIs
  • WebSocket APIs
  • HTTP APIs
  • Lambda
  • EC2
  • DynamoDB
  • CloudWatch
  • IAM

Only in Salt Edge

  • Account information
  • Payment initiation
  • Wide country coverage
  • Open Banking Gateway
  • Categorisation and enrichment
  • Consent management
  • Partner and white label
  • Sandbox

What people use each for

The jobs each tool is most often brought in to do.

AWS API Gateway

  • Fronting Lambda functions with an HTTP endpointnot Salt Edge
  • REST and HTTP API management with throttling and keysnot Salt Edge
  • WebSocket APIs for real-time clientsnot Salt Edge
  • Private APIs reachable only inside a VPCnot Salt Edge
  • Publishing a developer portal for API consumersnot Salt Edge

Salt Edge

  • A lender operating across several European and non-EU markets that needs one aggregation contract rather than a different provider per countrynot AWS API Gateway
  • A fintech that wants an aggregator not owned by a card network because its use case competes with card productsnot AWS API Gateway
  • An accounting or treasury product that needs bank feeds in markets the large aggregators do not servenot AWS API Gateway
  • A bank that must publish PSD2-compliant APIs and would rather buy the compliance layer than build itnot AWS API Gateway

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

AWS API Gateway

  • REST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer
  • Data transfer out is charged at $0.09 per GB on top of request pricing
  • WebSocket APIs bill connection minutes as well as messages, at $0.25 per million minutes
  • Private APIs avoid data transfer charges but incur AWS PrivateLink costs instead
  • The developer portal is $125 a month, with additional portal products at $12.50 each
  • The free tier lasts 12 months rather than being ongoing

Salt Edge

  • Coverage outside regulated open banking markets is not all direct bank API, and connections that are not regulated interfaces break when a bank changes its systems, so a headline country count overstates the reliability you will actually experience.
  • Pricing is not published and is usage-based, so two providers cannot be compared without running both sales processes, and cost grows with the connected user base rather than with revenue.
  • Support and engineering are distributed across Eastern Europe and Canada, and buyers in other time zones report slower turnaround on connection-specific breakages than they get from a domestic provider.
  • PSD2 consent rules require customers to reauthenticate periodically, and Salt Edge cannot change that, so any product depending on continuous data must design for consent expiry and the drop-off it causes.
  • United States coverage is weaker than Plaid or Mastercard Open Banking, so a company with meaningful US volume ends up running two aggregators and normalising between them.

Pricing, plan by plan

AWS API Gateway

Free
  • Free Tier (12 months)Free
    • 1M REST API calls per month
    • 1M HTTP API calls per month
    • 1M WebSocket messages plus 750K connection minutes per month
  • HTTP APIs$1/per million requests (first 300M)
    • First 300M: $1.00 per million
    • Next 132M: $0.90 per million
    • Data transfer varies by volume
  • REST APIs$3.5/per million API calls
    • Edge Optimized and Regional: $3.50 per million (first tier)
    • Higher volumes: $2.80 then $2.38 per million
    • Data transfer: $0.09 per GB
  • WebSocket APIs$1/per million messages
    • Messages: $1.00 per million
    • Connection minutes: $0.25 per million minutes

Salt Edge

On request
  • Salt Edge Open Banking API$undefined/year
    • Account information and payment initiation
    • Coverage across 50 plus countries
    • Consent management and enrichment

Which should you pick?

Choose AWS API Gateway if

  • You need rest apis.
  • You want to start without paying.
  • You work on AWS Cloud.
  • You also want websocket apis.

Choose Salt Edge if

  • You need account information.
  • You work on Web, API.
  • You also want payment initiation.

Questions people ask

Is AWS API Gateway or Salt Edge better?
Neither clearly leads. AWS API Gateway starts at Free and Salt Edge at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, AWS API Gateway or Salt Edge?
AWS API Gateway has a free tier; the other does not. Paid plans start at Free for AWS API Gateway and On request for Salt Edge.
Does AWS API Gateway or Salt Edge run on more platforms?
AWS API Gateway runs on AWS Cloud. Salt Edge runs on Web, API.
Can I use AWS API Gateway for free?
Yes. AWS API Gateway has a free tier, so you can try it without paying. Salt Edge starts at On request.
What is AWS API Gateway best used for?
AWS API Gateway is most often used for fronting lambda functions with an http endpoint, rest and http api management with throttling and keys, websocket apis for real-time clients, private apis reachable only inside a vpc. Of those, fronting lambda functions with an http endpoint and rest and http api management with throttling and keys are not what Salt Edge is typically brought in for.
What can AWS API Gateway do that Salt Edge cannot?
AWS API Gateway covers REST APIs, WebSocket APIs, HTTP APIs, Lambda. Salt Edge covers Account information, Payment initiation, Wide country coverage, Open Banking Gateway.

Answered from the vendors’ own pages

AWS API Gateway: How much does AWS API Gateway cost?

AWS API Gateway pricing varies by API type. HTTP APIs cost $1.00 per million requests for the first 300M monthly, then $0.90 per million. REST APIs cost $3.50 per million, and WebSocket APIs cost $1.00 per million messages plus $0.25 per million connection minutes. Data transfer charges ($0.09 per GB) apply separately.

Source
Salt Edge: Who owns Salt Edge?

It is independently owned, unlike Tink (Visa), Finicity (Mastercard) or Yodlee (Envestnet), which matters if your use case competes with the owner.

AWS API Gateway: Is AWS API Gateway free?

New AWS customers receive 12 months of free tier access including 1 million REST API calls, 1 million HTTP API calls, and 1 million WebSocket messages plus 750,000 connection minutes per month. Starting July 15, 2025, new customers receive up to $200 in AWS Free Tier credits.

Source
Salt Edge: Is all coverage direct bank API?

No. Inside PSD2 markets connections use regulated APIs; elsewhere coverage relies on direct connections whose reliability depends on the bank not changing its systems. Ask for a per-institution answer.

AWS API Gateway: What is the price difference between HTTP and REST APIs?

HTTP APIs are significantly cheaper at $1.00 per million requests compared to REST APIs at $3.50 per million (first tier). REST API pricing decreases to $2.80 and $2.38 per million for higher volumes, while HTTP API pricing drops to $0.90 per million after 300M monthly requests.

Source
Salt Edge: Does it do payments as well as data?

Yes, payment initiation is supported in European markets where PSD2 applies.

AWS API Gateway: How much does an API Gateway Portal cost?

API Gateway Portals require a base fee of $125 per month (includes 10 PortalProducts with 40 endpoints each) plus $12.50 per month for each additional PortalProduct beyond the included 10.

Source
Salt Edge: What does it cost?

Not published. Pricing is usage-based and quoted, though the sandbox is free.

Share

Related pages

Other head to heads