feat(integrations): Readwise APIs

[sarimabbas]

Added Readwise integration with support for both Readwise API (v2) and Readwise Reader API (v3)

• API key authentication for both APIs
• Documentation
• Provider logo

The Readwise API (v2) enables access to highlights and books data, while the Reader API (v3) allows saving and fetching documents in Readwise Reader.

• https://readwise.io/api_deets
• https://readwise.io/reader_api

[sarimabbas]

the v3 api still uses the v2/auth for verification, is it ok to have the full url like this? or will it lead to a bug i.e. https://readwise.io/api/v3/https://readwise.io/api/v2/auth ?

[bodinsamuel]

good question, we need to check

[sarimabbas]

I tried running Nango locally (using docker compose up). Readwise works but Readwise Reader does not work

Perhaps someone from the team would be willing to make a change that allows the endpoint to be a full URL or point me to the code, I am happy to take a stab at it

[nalanj]

From reading the code I think on the verification block you can set base_url_override and it will use that on verify.

See

nango/packages/server/lib/hooks/hooks.ts

Line 229 in b61728b

const { method, endpoint, base_url_override: baseUrlOverride, headers } = providerVerification;

[bodinsamuel]

good question, we need to check

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
8205899	Triggered	Generic Password	c3582ef	packages/cli/docker/docker-compose.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}