You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 7, 2025. It is now read-only.
Copy file name to clipboardexpand all lines: README.md
+4-8
Original file line number
Diff line number
Diff line change
@@ -29,14 +29,10 @@ This Next.js app authenticates the user and generates the [Decentralised ID Toke
29
29
**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.
30
30
5. yarn
31
31
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).
33
33
34
34
## 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.
36
36
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
-
[](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