Skip to content
This repository was archived by the owner on Feb 7, 2025. It is now read-only.

Commit 60b4ff1

Browse files
authored
Update README.md
1 parent e158284 commit 60b4ff1

File tree

1 file changed

+4
-8
lines changed

1 file changed

+4
-8
lines changed

README.md

+4-8
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,10 @@ This Next.js app authenticates the user and generates the [Decentralised ID Toke
2929
**Note**: The `HAPI_IRON_SECRET` is needed by @hapi/iron to encrypt an object. Feel free to leave the default value as is in dev.
3030
5. yarn
3131
6. yarn dev
32-
7. Generate your DID token and copy it (you'll need it soon).
32+
7. Generate your DID token and keep this open (you'll need it soon).
3333
3434
## Test with Postman
35-
**There are two options to test your DID token with the Scrappy Twitter API.** You could either follow the steps listed [here](https://github.com/seemcat/scrappy-twitter-api-server) to spin up your own local Go server.
35+
Follow the steps listed [here](https://github.com/seemcat/scrappy-twitter-api-server) to spin up your own local Go server and to set up the Scrappy Twitter API Postman Collection.
3636
37-
OR you can follow the steps below to immediately use your DID token on a Live Go server that is hosting the Scrappy Twitter API.
38-
39-
1. Import the PROD version of the Scrappy Twitter API Postman Collection:
40-
[![Run in Postman](https://run.pstmn.io/button.svg)](https://god.postman.co/run-collection/595abf685418eeb96401)
41-
3. Paste the DID token you just copied as a Bearer token into the collection’s HTTP Authorization request header.
42-
4. Send your requests to the **Live** Scrappy Twitter API! 🎉
37+
You'll be passing the DID token you just generated as a Bearer token into the Postman Collection’s HTTP Authorization request header.
38+
4. Send your requests to the **DEV** Scrappy Twitter API! 🎉

0 commit comments

Comments
 (0)