PipedreamHQ / PipedreamHQ/pipedream
Consent API
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
### App
Consent API
https://consent-api-stage1.onrender.com/docs
### Sources
None at this stage. Consent API is currently intended to be used through actions invoked from existing Pipedream workflows.
### Actions
a) Create Consent — Create a new consent record for a customer, application and business scenario.
b) Get Consent — Retrieve an existing consent record using its consent ID.
c) Get Consent Status — Retrieve the current status of a consent (ACTIVE, EXPIRED or REVOKED) using its consent ID.
d) Revoke Consent — Revoke an existing consent using its consent ID.
Contributor guide
Research direction
Start with the Consent API documentation at https://consent-api-stage1.onrender.com/docs and review the four listed actions: Create Consent, Get Consent, Get Consent Status, and Revoke Consent. Clarify the intended Pipedream workflow entry points and the expected scope before implementation; done should mean the agreed Consent API actions are usable through those workflows.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100