색인미확인수명주기 미확인품질 미측정구조화 한국어 안내 · 문장 번역 전

bunq API

bunq.com에서 제공하는 문서·기록 분야의 API 제품입니다. 확인된 분류 신호는 OCR·텍스트 추출, 결제·청구, 인증·계정, 이미지 데이터입니다.

영문 원문 보기
bunq API

UPDATE: We have released a [beta version of the new bunq API documentation.](https://beta.doc.bunq.com) NOTICE: We have updated the sandbox base url to https://public-api.sandbox.bunq.com/v1/ . Please update your applications accordingly. Check here: for more info. PSD2 NOTICE: The second Payment Services Directive (PSD2) may affect your current or planned usage of our public API, as some of the API services are now subject to a permit. Please be aware that using our public API without the required PSD2 permit is at your own risk and take notice of our updated API Terms and Conditions on for more information. Introduction Welcome to bunq! - The bunq API is organised around REST. JSON will be returned in almost all responses from the API, including errors but excluding binary (image) files. - Please configure your implementation to send its API requests to https://public-api.sandbox.bunq.com/v1/ - There is a version of the [Android app](https://appstore.bunq.com/api/android/builds/bunq-android-sandbox-master.apk) that connects to the bunq Sandbox environment. To create accounts for the Sandbox app, please follow the steps in the [Android Emulator]( android-emulator) section. Getting started Before you start sending API requests, you need to get an API key and activate it. API activation happens when you install the API key and link your IP address and device to it (create an API context) . The steps below will guide you through what you need to do to start sending custom API requests. Here is an overview of what you can use to get started with the bunq API: 1. Create an API key. You can do it either in our [developer portal](https://developer.bunq.com) or in the bunq app (Profile → Security & Settings → Developers → API keys) . If you want to test our sandbox first, our [bunq Developer ](https://developer.bunq.com)is the best place to start. 2. Register a device. A device can be a phone (private), computer or a server (public). You can register a new device by using the POST /installation and POST /device-server calls. This will activate your API key. You only need to do this once. 3. Open a session. Sessions are temporary and expire after the auto-logout time set for the user account. It can be changed by the account owner in the bunq app. 4. Make your first call! ![bunq API context](https://www.bunq.com/assets/media/developer/API-context.jpg) Versioning Developments in the financial sector, changing regulatory regimes and new feature requests require us to be flexible. This means we can iterate quickly to improve the API and related tooling. Therefore, we have chosen not to attach any version numbers to the changes just yet. We will inform you in a timely manner of any important changes we make before they are deployed on together.bunq.com. You can also [subscribe to our API newsletter](https://bunq.us8.list-manage.com/subscribe?u=c00d0d6daea4e1cf7c863d52e&id=b08680cdc7) to make sure you don't miss any important updates. OAuth What is OAuth? [OAuth 2.0](https://www.oauth.com/oauth2-servers/getting-ready/) is a protocol that will let your app connect to bunq users in a safe and easy way. Please be aware that if you will gain access to the account information of other bunq users or initiate a payment for them, [you may require a PSD2 permit](https://beta.doc.bunq.com/other/faq can-we-use-the-bunq-api-to-offer-services-to-third-parties). Get started with OAuth for bunq To initiate authorization into the bunq user accounts, you need to create an OAuth Client and register at least 1 redirect URL for it. You can have 1 OAuth Client at a time. Reuse your OAuth credentials for every authorization request. The list of steps below will help you to get started: 1. Register an OAuth Client by creating an app in [bunq Developer](https://developer.bunq.com/portal) . 2. Add one or more Redirect URLs. 3. Get your client id and secret from your app information tab in [bunq Developer](https://developer.bunq.com/portal). 4. Redirect your users…

번역은 이해를 돕기 위한 미검수 초벌 또는 구조화 안내입니다. 계약·의료·법률 판단에는 원문을 확인하세요.
연결된 문서
전역 집계 전현재 별표는 이 브라우저에만 저장
종합 품질근거 0%
가격미확인상세 가격 미수집
인증미확인
프로토콜REST429개 엔드포인트 수집
마지막 확인2026. 7. 28.출처 확인됨

SELECTION SUMMARY

도입 판단 요약

이 항목은 문서·기록 카테고리로 분류된 API 제품입니다. 확인된 분류 신호는 OCR·텍스트 추출, 결제·청구, 인증·계정, 이미지 데이터입니다. 상세 문장 번역은 아직 검수되지 않았으므로 아래 원문을 함께 확인하세요.

검수된 적합 용도

검증 정보 없음 — 태그와 카테고리는 분류 정보이며 적합성 보증이 아닙니다.

도입 전 확인

인증, 호출 제한, 데이터 처리 지역과 가격 조건을 연결된 문서에서 직접 확인하세요.

피해야 할 조건

제품별 제한 조건이 검수되지 않았습니다. 운영 적용 전에 공급자 조건을 재확인하세요.

EVIDENCED ADVANTAGES

API 특·장점

공급자·카탈로그·실측·편집 근거가 있는 신호만 표시하며, 근거 유형을 함께 밝힙니다.

카탈로그출처가 확인된 제품

카탈로그 원본과 확인 시점이 연결되어 있습니다.

공급자OpenAPI 3.0.0

정규화된 엔드포인트 429개를 탐색할 수 있습니다.

CATALOG TRUST

색인0

재배포 정책과 기본 식별 조건을 통과해 검색할 수 있지만 편집 승인은 아직 완료되지 않았습니다.

평가 2026. 07. 28. 13:05

QUALITY COVERAGE

미측정종합 점수
근거 충족률 0% · 신뢰 0%

unrated

핵심 도입 정보

인증검증 정보 없음
프로토콜REST
가격 모델미확인
리전검증 정보 없음
수집된 엔드포인트429개
마지막 확인2026. 07. 28. 13:05

같은 목적의 대체 API

같은 카테고리에서 공개 상태와 품질 근거를 우선해 표시합니다.