Skip to content
agentusehub
Sign in+ Submit
Software & DevOpsAny

Add a third-party API integration via Devin PR

Devin opened a PR with the endpoint and backend wiring that was merged, but missed API key logic, code style and abstraction, needing review fixes.

Read the experience
Time saved
Not reported
Setup time
Not reported
Running cost
Not reported
Cost range
Not reported

Use case overview

Devin opened a PR with the endpoint and backend wiring that was merged, but missed API key logic, code style and abstraction, needing review fixes.

Read the original report ↗

Reported experience

  1. What they did

    The author asked Devin, through its Slack integration, to build a token-generation endpoint for a third-party service from the docs link. The prompt said to add it to an existing microservice and use the existing CDK secrets logic for the API key. Devin posted a plan, then opened a GitHub PR. The author left review comments on the PR, and Devin pushed fixes.

  2. How it went

    After 2-3 review rounds the code was production-ready, tests passed, and the PR merged. The whole task took about an hour, against roughly 15 minutes if done by hand. The author spent about 5 minutes reviewing.

  3. Worth knowing

    Devin left out the third-party API key in its calls and didn't put the client logic in the shared clients library, so review the PR as you would a junior's.

Example prompts

Try with Devin
In the repo [repo URL], add an integration with [third-party API] including the endpoint, backend wiring, and config for the API key via [env var or secrets approach]. Follow the existing code style and abstractions in [folder or file] and add tests. Open a pull request listing what you changed and any assumptions, and stop there without merging.

Related use cases

Software & DevOps

Port a Chrome extension to Safari

The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.

ChatGPT