Where do I get the source ID

Help
3

Yes! Thanks. That’s what I needed. I am trying to access this source with the following code:

https://api.pipedream.com/v1/sources/dc_lVuM0Z7/event_summaries?expand=event
-H "Authorization: Bearer "

where MyAPIKey is substituted with the actual key.

I am getting the following error in the global field set to receive the reply: {“error”:“record not found”} If this were an error coming from my system, I would normally see it in my system as an error and I am not. So, I am checking with you to see if this error might indicate something wrong in my syntax or something else at your end.

Thanks for the continued help.
Seth

4

Opps. the MyAPIKey part of the syntax got deleted when the message was sent. Sorry about that. I think it is correct though.

5

Sorry for the late reply, Seth. That URL looks correct. I would just double check that you’re logged into the same account where your source exists, and then navigate to your settings and confirm you’re using the correct API key.

And just to confirm, are you making a GET request for the URL?

6

Thanks for the reply. I can confirm that the URL is correct. There may other issues which you can help with. Here is the text stream I am seeing. Can you see anything that needs attention?

== Info: Trying 3.222.50.60:443…
== Info: Connected to api.pipedream.com (3.222.50.60) port 443 (#0)
== Info: ALPN, offering http/1.1
== Info: Cipher selection: ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
=> Send SSL data, 5 bytes (0x5)
0000: …
== Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):
=> Send SSL data, 512 bytes (0x200)
0000: …T…F]…h.k4u…b5y…{$.n;R… 8…t*…j… .DnG…
0040: .f…/.+.0.,…’.#…(.$…g.3.@.k.8.9…
0080: <.=./.5…j.2…W…api.pipedream.
00c0: com…3t…http/1.1…1…0…
0100: …+…-…
0140: …3.&.$… .’…WTe’;N$|’…B.M…S.N…R…
0180: …
01c0: …
<= Recv SSL data, 5 bytes (0x5)
0000: …h
== Info: TLSv1.3 (IN), TLS handshake, Server hello (2):
<= Recv SSL data, 104 bytes (0x68)
0000: …d…>C$P…p…:$hU…O…9v.>{1.K 1].._....^O.%f...q...#..4 0040: =..G..../.......................http/1.1 <= Recv SSL data, 5 bytes (0x5) 0000: ..... == Info: TLSv1.2 (IN), TLS handshake, Certificate (11): <= Recv SSL data, 4857 bytes (0x12f9) 0000: ..........0...0..n........_.t..C&..(.U.};0...*.H........0F1.0... 0040: U....US1.0...U....Amazon1.0...U....Server CA 1B1.0...U....Amazon 0080: 0...210305000000Z..220403235959Z0.1.0...U....api2.pipedream.com0 00c0: .."0...*.H.............0.........o.,......'8.cG.|.a?.i1I........ 0100: ...G<...s..~....#...l..^w..e$.2T{.m..@....,.?........*.9:Jl..... 0140: .C..x..YE...$.S........".......3YN.p.....@.^..$o..r1.L.......... 0180: .....h~(J.0...J.......kmD.&}.-..e.(5~..v.-n...W.....G.....C.PQY. 01c0: o...=.%.b...T..^.sE..hMi_fs..X,..........0...0...U.#..0...Y.f.R. 0200: {..<...'.t[.=.0...U......Z.._S.<C.a.S]..1....0C..U...<0:..api2.p 0240: ipedream.com..api.pipedream.net..api.pipedream.com0...U......... 0280: ..0...U.%..0...+.........+.......0;..U...40200...,.*http://crl.s 02c0: ca1b.amazontrust.com/sca1b.crl0...U. ..0.0...g.....0u..+........ 0300: i0g0-..+.....0..!http://ocsp.sca1b.amazontrust.com06..+.....0..* 0340: http://crt.sca1b.amazontrust.com/sca1b.crt0...U.......0.0.....+. 0380: ....y............v.F.U.u.. 0...i..}.,At..I.....p.mG...x.N5...... 03c0: G0E. :.......W.......M.n.h.m......3m..!......>D.........2.0..... 0400: x..K.d.>.v."EE.YU$V.?./..m..#&c..K.]..\n......x.N5g.....G0E. @!< 0440: .:5.hhs..%..L...Y~-.e…F.8.!..]…0…Q~…H.+…
0480: 0….H…j…j@=.^…p.b…sq7…d…8.>:.q…
04c0: …!.d"@…t…(%…J…U.,/kgn…bX…?.Qe7…'v.
0500: .M…i…3506….k'..[P..d2T....q..1....d..U...k5.*.x....^@...v.. 0540: BO..*....,......?.....E.0..^_.~…b…\EB?..24.T8…}O..c.. 0580: .y...GH.....C.\.HW....M0..I0..1..........W....w..S2[...V.0...*.H 05c0: ........091.0...U....US1.0...U....Amazon1.0...U....Amazon Root C 0600: A 10...151022000000Z..251019000000Z0F1.0...U....US1.0...U....Ama 0640: zon1.0...U....Server CA 1B1.0...U....Amazon0.."0...*.H.......... 0680: ...0.........N.g...j.7Z.:0.......(H..)..nS....9..w.....p..k....q 06c0: ..m...*N........<..9...X...V%.>Rz..)...nP.._1....Jb...>G..'... . 0700: ....5._..M.k7..P>D..Z.f..~.jU...5.....uNXU}Sk.k..B...........+.. 0740: ..S..g....:..s._...r.~...0c*..z-......2>.....<...P..C..*..h....J 0780: e.J...L.U...........;0..70...U.......0.......0...U...........0.. 07c0: .U......Y.f.R.{..<...'.t[.=.0...U.#..0.......4.......Y....N..0{. 0800: .+........o0m0/..+.....0..#http://ocsp.rootca1.amazontrust.com0: 0840: ..+.....0...http://crt.rootca1.amazontrust.com/rootca1.cer0?..U. 0880: ..80604.2.0..http://crl.rootca1.amazontrust.com/rootca1.crl0...U 08c0: . ..0.0...g.....0...*.H................5.y...B...csS9R5......... 0900: ./..o..Nr. 0a.....'.E..v>.J....E..C...m.n.1.../1..ma7{X..Q..(.O. 0940: v......^.f........). H…Se5…k.Q@UW_…">…^…AZ.R…6.
0980: O-…h5…r…}W.y.7.{....-.w.I.'.8.......H.........vR...Axp.m. 09c0: .J.x-^...L…G.x-…R…9,…/.3…0…0…z…J’…
0a00: .+…0….H…0…1.0…U…US1.0…U…Arizona1.0…
0a40: U…Scottsdale1%0#…U…Starfield Technologies, Inc.1;09…U…
0a80: 2Starfield Services Root Certificate Authority - G20…150525120
0ac0: 000Z…371231010000Z091.0…U…US1.0…U…Amazon1.0…U…Am
0b00: azon Root CA 10…"0….H…0…x.q.x…q.G.Pt}n.
0b40: …v…h.X!.t../..-...CzN...6.....H...6L...#.>.7....Ih....v8.a... 0b80: .6..JV.E......t...59/.. P.lz.......G..P8....9X.....Hg0...x^o..Q. 0bc0: 0.f.Ef.T.....H....0-}-tp5..$...Yn.s...2F(.C........$.-K.q\^i.... 0c00: .8..P8o..-b....T.w.g....#.?@ . ...L>;$&...l............10..-0... 0c40: U.......0....0...U...........0...U..........4.......Y....N..0... 0c80: U.#..0...._.....0+8...mJ.....0x..+........l0j0...+.....0.."http: 0cc0: //ocsp.rootg2.amazontrust.com08..+.....0..,http://crt.rootg2.ama 0d00: zontrust.com/rootg2.cer0=..U...60402.0...,http://crl.rootg2.amaz 0d40: ontrust.com/rootg2.crl0...U. ..0.0...U. .0...*.H.............b7B 0d80: \...>.,...lE...z..X....>..%<.oP..5j..4.2!.HD...=..sm.....l.(...G 0dc0: y..~0[.;..w…|^…{"…~.F…&W.09b…>.ChlW… …
0e00: …j]…Jm.X…91_|s…j…’…F.~.r…R>…cw.i…9…EM.Q:.]]7dL
0e40: ~0.U$B.6.]…a…$…t…{E)P9…5%…jG#1/…bQ.…4.!..y
0e80: 0…u0…]…JL4…0….H…0h1.0…U…US1%0#…U…
0ec0: .Starfield Technologies, Inc.1200…U…)Starfield Class 2 Certif
0f00: ication Authority0…090902000000Z…340628173916Z0…1.0…U…U
0f40: S1.0…U…Arizona1.0…U…Scottsdale1%0#…U…Starfield Tec
0f80: hnologies, Inc.1;09…U…2Starfield Services Root Certificate Au
0fc0: thority - G20…"0….H…0…:..N……S…?
1000: … .m):…}<.kv8c.6..^\.../Y....%C..i.R...q..-.No..I....V.+.t.. 1040: ..&......j;X..GV.%..pS...t..g..h:..@Z.JN.C.;.V..p.R.{}.:..1.E..
1080: …Y.+…4G…em…,…I|fN.:m…4…3.G…k.%…EF2.p…I
10c0: C…ls.d.aA…T…/.".&…YTh…*/.U.u@...U9...........0..0...U... 1100: ....0....0...U...........0...U......._.....0+8...mJ.....0...U.#. 1140: .0...._.......[U.........0O..+........C0A0...+.....0...http://o. 1180: ss2.us/0!..+.....0...http://x.ss2.us/x.cer0&..U....0.0.......htt 11c0: p://s.ss2.us/r.crl0...U. ..0.0...U. .0...*.H.............#...W.} 1200: ..yL..U..Sn>G...U...6...S.]4(k..U.g..?...3..X...../..…u
1240: .O…m…~@,…v.3.w…S…d…’.i.M^…u.XD-.<p…i…w…1^,.
1280: …:Gi.y…T…^.x.'...w.#Sw]...Y.......$.5.z....}..?...rT....Y{. 12c0: .R.F...dv.H..y.nV..,....8.....[......4I.V..._.3..G.0.]... <= Recv SSL data, 5 bytes (0x5) 0000: ....M == Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12): <= Recv SSL data, 333 bytes (0x14d) 0000: ...I...A..~.<i.Z.yW...J..L.5.......l...l......K.....hZ.D....?.gX 0040: r...X!............]z...(P.C....d.!...fg..%p|..o<ue.~.n.........{ 0080: ..R.E.8!..!_…w.$+…D…&/…<.E…~…O…#…kr.rz]…Z.
00c0: .B…bbF…-…%…9…....a.cc...FLR.(k.P.yp... 0100: t.;.Z.t.......%.y..j.rE...y....3d..@..mZG..24...v.[nq.h;.y.Ek.r. 0140: .(hp./9…
<= Recv SSL data, 5 bytes (0x5)
0000: …
== Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
<= Recv SSL data, 4 bytes (0x4)
0000: …
=> Send SSL data, 5 bytes (0x5)
0000: …F
== Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
=> Send SSL data, 70 bytes (0x46)
0000: …BA…w…B.nH…C.J…l…wt.,…s…~(…]……c].Z
0040: …. => Send SSL data, 5 bytes (0x5) 0000: ..... == Info: TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): => Send SSL data, 1 bytes (0x1) 0000: . => Send SSL data, 5 bytes (0x5) 0000: ....( == Info: TLSv1.2 (OUT), TLS handshake, Finished (20): => Send SSL data, 16 bytes (0x10) 0000: ....=....3.~O9.. <= Recv SSL data, 5 bytes (0x5) 0000: ..... <= Recv SSL data, 5 bytes (0x5) 0000: ....( == Info: TLSv1.2 (IN), TLS handshake, Finished (20): <= Recv SSL data, 16 bytes (0x10) 0000: ....-.?&...G..i6 == Info: SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 == Info: ALPN, server accepted to use http/1.1 == Info: Server certificate: == Info: subject: CN=api2.pipedream.com == Info: start date: Mar 5 00:00:00 2021 GMT == Info: expire date: Apr 3 23:59:59 2022 GMT == Info: issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon == Info: SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. => Send SSL data, 5 bytes (0x5) 0000: ..... => Send header, 224 bytes (0xe0) 0000: GET /v1/sources/dc_lVuM0Z7/event_summaries?expand=event HTTP/1.1 0042: Host: api.pipedream.com 005b: User-Agent: FileMaker/19.3 0077: Accept: */* 0084: Accept-Encoding: deflate, gzip 00a4: Authorization: Bearer <xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 00de: <= Recv SSL data, 5 bytes (0x5) 0000: ..... == Info: Mark bundle as not supporting multiuse <= Recv header, 24 bytes (0x18) 0000: HTTP/1.1 404 Not Found <= Recv header, 37 bytes (0x25) 0000: Date: Mon, 12 Jul 2021 16:21:50 GMT <= Recv header, 47 bytes (0x2f) 0000: Content-Type: application/json; charset=utf-8 <= Recv header, 28 bytes (0x1c) 0000: Transfer-Encoding: chunked <= Recv header, 24 bytes (0x18) 0000: Connection: keep-alive <= Recv header, 31 bytes (0x1f) 0000: Vary: Accept-Encoding, Origin <= Recv header, 24 bytes (0x18) 0000: Content-Encoding: gzip <= Recv header, 25 bytes (0x19) 0000: Cache-Control: no-cache <= Recv header, 52 bytes (0x34) 0000: X-Request-Id: 84e5fae2-4b02-48b4-8eeb-ecf442535436 <= Recv header, 21 bytes (0x15) 0000: X-Runtime: 0.004446 <= Recv header, 2 bytes (0x2) 0000: <= Recv data, 60 bytes (0x3c) 0000: 36 0004: .....l.…VJ-./R.R*JM./JQ…/QH./.KQ…L.v…
<= Recv SSL data, 5 bytes (0x5)
0000: …
<= Recv data, 5 bytes (0x5)
0000: 0
0003:
== Info: Connection #0 to host api.pipedream.com left intact

7

I don’t see anything that looks off with that request. I’d recommend visiting your account settings and revoking your API key, which will generate a new key. Try using that new API key to make the request and let me know if that works.

8

Thanks for the suggestion. I revoked the API Key and installed the new one in my code and got the same response: {“error”:“record not found”}. This is the same response I get when I try the URL in a browser that is not logged in to Pipedream. This suggests that the problem is an authentication issue. But, it appears from the text I sent previously that the authentication is working, right? Not sure where to go from here. What about these lines in the text:

== Info: Mark bundle as not supporting multiuse
<= Recv header, 24 bytes (0x18)
0000: HTTP/1.1 404 Not Found

Are they at all significant?

9

Could you tell me the Pipedream username you see in the bottom-left of the Pipedream UI when you’re on your account settings?

10

Looks like @seth-parellifoundation.

11

Thanks. I do see that account owns the source ID you’re trying to pull data for. The reason I asked is that I’m seeing two accounts tied to your email address (this one, and another based on your Google login). I was concerned you might be sending the API key for the other, Google-based account (parellifoundation100). That would explain the 404 you’re observing, since you’d be trying to use an API key to fetch a resource you don’t own.

12

That’s a good thought, although I am not sure how I ended up with two accounts. It looks like I am using parellifoundation100 to access this community and seth-parellifoundation to access my active account.

13

I tried a less complicated API request. ‘https://api.pipedream.com/v1/users/me’ I got the same response. And the detailed text looks about the same. See attached file. API key removed. I really can’t think of where to go from here.

== Info: Trying 34.225.209.84:443…
== Info: Connected to api.pipedream.com (34.225.209.84) port 443 (#0)
== Info: ALPN, offering http/1.1
== Info: Cipher selection: ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA
=> Send SSL data, 5 bytes (0x5)
0000: …
== Info: TLSv1.3 (OUT), TLS handshake, Client hello (1):
=> Send SSL data, 512 bytes (0x200)
0000: …h#UA…X…di;.Y…D#.,.N…]… .z}…6…2.#….6.j.l.m... 0040: ...{....\......./.+.0.,.........'.#.....(.$.....g.3.@.k.8.9..... 0080: <.=./.5.................j.2.............W.........api.pipedream. 00c0: com........................3t.........http/1.1.........1.....0.. 0100: ...............................................+............-... 0140: ..3.&.$... ..7...+........5.!....K........+..................... 0180: ................................................................ 01c0: ................................................................ <= Recv SSL data, 5 bytes (0x5) 0000: ....h == Info: TLSv1.3 (IN), TLS handshake, Server hello (2): <= Recv SSL data, 104 bytes (0x68) 0000: ...d......q..i.2..…E…S…d…?..e^U .!..i…CX……
0040: "XI…/…http/1.1
<= Recv SSL data, 5 bytes (0x5)
0000: …
== Info: TLSv1.2 (IN), TLS handshake, Certificate (11):
<= Recv SSL data, 4857 bytes (0x12f9)
0000: …0…0…n…_.t…C&…(.U.};0….H…0F1.0…
0040: U…US1.0…U…Amazon1.0…U…Server CA 1B1.0…U…Amazon
0080: 0…210305000000Z…220403235959Z0.1.0…U…api2.pipedream.com0
00c0: …“0….H…0…o.,…'8.cG.|.a?.i1I…
0100: …G<…s…~…#…l…^w…e$.2T{.m…@…,.?...9:Jl…
0140: .C…x…YE…$.S…”…3YN.p…@.^…$o…r1.L…
0180: …h~(J.0…J…kmD.&}.-…e.(5~…v.-n…W…G…C.PQY.
01c0: o…=.%.b…T…^.sE…hMi_fs…X,…0…0…U.#…0…Y.f.R.
0200: {…<…’.t[.=.0…U…Z…S.<C.a.S]…1…0C…U…<0:…api2.p
0240: ipedream.com…api.pipedream.net…api.pipedream.com0…U…
0280: …0…U.%…0…+…+…0;…U…40200…,.http://crl.s
02c0: ca1b.amazontrust.com/sca1b.crl0...U. …0.0…g…0u…+…
0300: i0g0-…+…0…!http://ocsp.sca1b.amazontrust.com06…+…0…
0340: http://crt.sca1b.amazontrust.com/sca1b.crt0...U…0.0…+.
0380: …y…v.F.U.u… 0…i…}.,At…I…p.mG…x.N5…
03c0: G0E. :…W…M.n.h.m…3m…!..>D…2.0…
0400: x…K.d.>.v."EE.YU$V.?./…m…#&c…K.]…\n…x.N5g…G0E. @!<
0440: .:5.hhs…%…L…Y~-.e....F.8.!..].........0....Q~..H.+......... 0480: 0...*.H.............j...j@=.^..p.b...sq7........d....8.>:.q..... 04c0: ......!.d"@...t....(%.....J.....U.,/kgn..bX...........?.Qe7..'v. 0500: .M..i..3506....k’…[P…d2T…q…1…d…U…k5..x…^@…v…
0540: BO……,…?..E.0…^.~..b.......\EB?..24.T8...}O…c…
0580: .y…GH…C…HW…M0…I0…1…W…w…S2[…V.0….H
05c0: …091.0…U…US1.0…U…Amazon1.0…U…Amazon Root C
0600: A 10…151022000000Z…251019000000Z0F1.0…U…US1.0…U…Ama
0640: zon1.0…U…Server CA 1B1.0…U…Amazon0…"0….H…
0680: …0…N.g…j.7Z.:0…(H…)…nS…9…w…p…k…q
06c0: …m…N…<…9…X…V%.>Rz…)…nP…1…Jb…>G…’… .
0700: …5.…M.k7…P>D…Z.f…~.jU…5…uNXU}Sk.k…B…+…
0740: …S…g…:…s._…r.~…0c…z-…2>…<…P…C……h…J
0780: e.J…L.U…;0…70…U…0…0…U…0…
07c0: .U…Y.f.R.{…<…’.t[.=.0…U.#…0…4…Y…N…0{.
0800: .+…o0m0/…+…0…#http://ocsp.rootca1.amazontrust.com0:
0840: …+…0…http://crt.rootca1.amazontrust.com/rootca1.cer0?..U.
0880: …80604.2.0…http://crl.rootca1.amazontrust.com/rootca1.crl0...U
08c0: . …0.0…g…0….H…5.y…B…csS9R5…
0900: ./…o…Nr. 0a…’.E…v>.J…E…C…m.n.1…/1…ma7{X…Q…(.O.
0940: v…^.f…). H.....Se5..k.Q@UW_...">..^.......AZ.R...6. 0980: O-...h5..r....}W.y.7.{…-.w.I.’.8…H…vR…Axp.m.
09c0: .J.x-^…L..G.x-...R..9,../.3.........0...0..z..........J*'.... 0a00: .+.......0...*.H........0..1.0...U....US1.0...U....Arizona1.0... 0a40: U....Scottsdale1%0#..U....Starfield Technologies, Inc.1;09..U... 0a80: 2Starfield Services Root Certificate Authority - G20...150525120 0ac0: 000Z..371231010000Z091.0...U....US1.0...U....Amazon1.0...U....Am 0b00: azon Root CA 10.."0...*.H.............0.........x.q.x..q.G.Pt}n. 0b40: ..v..h.X!.t…/…-…CzN…6…H…6L…#.>.7…Ih…v8.a…
0b80: .6…JV.E…t…59/… P.lz…G…P8…9X…Hg0…x^o…Q.
0bc0: 0.f.Ef.T…H…0-}-tp5…$…Yn.s…2F(.C…$.-K.q^i…
0c00: .8…P8o…-b…T.w.g…#.?@ . …L>;$&…l…10…-0…
0c40: U…0…0…U…0…U…4…Y…N…0…
0c80: U.#…0……0+8…mJ…0x…+…l0j0…+…0…"http:
0cc0: //ocsp.rootg2.amazontrust.com08…+…0…,http://crt.rootg2.ama
0d00: zontrust.com/rootg2.cer0=..U...60402.0…,http://crl.rootg2.amaz
0d40: ontrust.com/rootg2.crl0...U. …0.0…U. .0…*.H…b7B
0d80: …>.,…lE…z…X…>…%<.oP…5j…4.2!.HD…=…sm…l.(…G
0dc0: y…~0[.;..w.....|^....{"....~.F....&W.09b.........>.ChlW.... .. 0e00: ..j]..Jm.X...91_|s...j...'....F.~.r..R>...cw.i..9....EM.Q:.]]7dL 0e40: ~0.U$B.6.]...a.....$...t..{E)P9....5%..jG#1/\.....bQ.*...4.!...y 0e80: 0..u0..]..........JL4...0...*.H........0h1.0...U....US1%0#..U... 0ec0: .Starfield Technologies, Inc.1200..U...)Starfield Class 2 Certif 0f00: ication Authority0...090902000000Z..340628173916Z0..1.0...U....U 0f40: S1.0...U....Arizona1.0...U....Scottsdale1%0#..U....Starfield Tec 0f80: hnologies, Inc.1;09..U...2Starfield Services Root Certificate Au 0fc0: thority - G20.."0...*.H.............0..........:.*.N....._..S..? 1000: ... .m):..}<.kv8c.6…^…/Y…%C…i.R…q…-.No…I…V.+.t…
1040: …&…j;X…GV.%…pS…t…g…h:…@Z.JN.C.;.V…p.R.{}.:…1.E… 1080: ..Y.+..4G....em..,.......I|fN.:m...4.....3.G..k.%.....EF2.p....I 10c0: C..ls.d.aA...T../.".&..YTh...*/.U.u@…U9…0…0…U…
1100: …0…0…U…0…U……0+8…mJ…0…U.#.
1140: .0……[U…0O…+…C0A0…+…0…http://o. 1180: ss2.us/0!..+…0…http://x.ss2.us/x.cer0&..U....0.0…htt 11c0: p://s.ss2.us/r.crl0…U. …0.0…U. .0…*.H…#…W.} 1200: …yL…U…Sn>G…U…6…S.]4(k…U.g…?..3…X…/….........u 1240: .O..m......~@,....v.3.w....S..d..'.i.M^....u.XD-.<p...i..w..1^,. 1280: ..:Gi.y_..T..^.x.’…w.#Sw]…Y…$.5.z…}…?..rT…Y{.
12c0: .R.F…dv.H…y.nV…,…8…[…4I.V….3…G.0.]…
<= Recv SSL data, 5 bytes (0x5)
0000: …M
== Info: TLSv1.2 (IN), TLS handshake, Server key exchange (12):
<= Recv SSL data, 333 bytes (0x14d)
0000: …I…A.;…b.:…h…e.o*.T.K.t4.M.7…V-.q…b
0040: .#h!..>I…).j(r8z…Vr…1.c…0.ak.7…l6#…’.G…h+…x.d.W.Je
0080: …g…4…0.J.s."…$Q6.r.^%…O…3.G…A~…2.Hr#Z
00c0: …j.34…7_…0>.~.a…BP.YTx.csq…d.V. .o.(zL…S…h…m…
0100: .+…q…L.K…+g…s.S2.6…J…Z…k…>…l
0140: :a1C…5./2S@
<= Recv SSL data, 5 bytes (0x5)
0000: …
== Info: TLSv1.2 (IN), TLS handshake, Server finished (14):
<= Recv SSL data, 4 bytes (0x4)
0000: …
=> Send SSL data, 5 bytes (0x5)
0000: …F
== Info: TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
=> Send SSL data, 70 bytes (0x46)
0000: …BA…m…M"%.t.8…;EY…^…2…1…:.-…1…).=…7…
0040: m.r…
=> Send SSL data, 5 bytes (0x5)
0000: …
== Info: TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
=> Send SSL data, 1 bytes (0x1)
0000: .
=> Send SSL data, 5 bytes (0x5)
0000: …(
== Info: TLSv1.2 (OUT), TLS handshake, Finished (20):
=> Send SSL data, 16 bytes (0x10)
0000: …_…i’. <= Recv SSL data, 5 bytes (0x5) 0000: ..... <= Recv SSL data, 5 bytes (0x5) 0000: ....( == Info: TLSv1.2 (IN), TLS handshake, Finished (20): <= Recv SSL data, 16 bytes (0x10) 0000: .......Z........ == Info: SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 == Info: ALPN, server accepted to use http/1.1 == Info: Server certificate: == Info: subject: CN=api2.pipedream.com == Info: start date: Mar 5 00:00:00 2021 GMT == Info: expire date: Apr 3 23:59:59 2022 GMT == Info: issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon == Info: SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. => Send SSL data, 5 bytes (0x5) 0000: ..... => Send header, 184 bytes (0xb8) 0000: GET /v1/users/me HTTP/1.1 001b: Host: api.pipedream.com 0034: User-Agent: FileMaker/19.3 0050: Accept: */* 005d: Accept-Encoding: deflate, gzip 007d: Authorization: Bearer <XXXXXXXXXXXXXXXXXXXXXXX> 00b6: <= Recv SSL data, 5 bytes (0x5) 0000: ..... == Info: Mark bundle as not supporting multiuse <= Recv header, 24 bytes (0x18) 0000: HTTP/1.1 404 Not Found <= Recv header, 37 bytes (0x25) 0000: Date: Thu, 15 Jul 2021 16:11:32 GMT <= Recv header, 47 bytes (0x2f) 0000: Content-Type: application/json; charset=utf-8 <= Recv header, 28 bytes (0x1c) 0000: Transfer-Encoding: chunked <= Recv header, 24 bytes (0x18) 0000: Connection: keep-alive <= Recv header, 31 bytes (0x1f) 0000: Vary: Accept-Encoding, Origin <= Recv header, 24 bytes (0x18) 0000: Content-Encoding: gzip <= Recv header, 25 bytes (0x19) 0000: Cache-Control: no-cache <= Recv header, 52 bytes (0x34) 0000: X-Request-Id: 61b3ed80-30bc-4f25-bbfd-f0f625d65b63 <= Recv header, 21 bytes (0x15) 0000: X-Runtime: 0.003278 <= Recv header, 2 bytes (0x2) 0000: <= Recv data, 60 bytes (0x3c) 0000: 36 0004: ....4^.…VJ-./R.RJM./JQ…/QH./.KQ…L.v…
<= Recv SSL data, 5 bytes (0x5)
0000: …
<= Recv data, 5 bytes (0x5)
0000: 0
0003:
== Info: Connection #0 to host api.pipedream.com left intact

14

Do you happen to have a command-line client like cURL installed on your machine? I’d like to see if that works:

curl 'https://api.pipedream.com/v1/users/me' \
  -H 'Authorization: Bearer <api_key>'

Also, just to confirm, when you send your API key, are you surrounding it with <>? That is, are you sending it like this:

Authorization: Bearer 123

or this:

Authorization: Bearer <123>
15

Thanks so much for the continued help. I was thinking the same thing when your message came in. I am on Windows. I tried using Power Shell to connect to the API, but discovered that Power Shell has some reserved characters that make connecting difficult. Thanks to your suggestion, I found that I have the curl app on my computer (comes with Windows these days). Here is what I got when I used curl on the command line.

C:\Users\Seth>curl “https://api.pipedream.com/v1/users/me” \ -H 'Authorization: Bearer ’
The system cannot find the file specified.

I left the API key in this time, so you can see the exact syntax. I will change the API key when we get this figured out.

16

Thanks, Seth. Could you try sending the API key without the <>?

Authorization: Bearer 123

The <> is meant to be a part of the API key and indicate that you fill in your own API key. Let me know if that works for you.

17

Thanks for clarifying this. I did discover a missing leading 1 from the API Key. Here is the result with the correct key and brackets removed.

C:\Users\Seth>curl “https://api.pipedream.com/v1/users/me” \ -H Authorization: Bearer XXX
{“error”:“record not found”}curl: (6) Could not resolve host:
curl: (6) Could not resolve host: Bearer
curl: (6) Could not resolve host: XXX

18

You’ll need to surround the Authorization header / value with quotes to have it passed to the API correctly. The way it is now, cURL is trying to send HTTP requests to those values:

curl: (6) Could not resolve host: Bearer
curl: (6) Could not resolve host: XXX

But you’ll want to run:

curl “https://api.pipedream.com/v1/users/me” -H 'Authorization: Bearer API_KEY'

Let me know if that makes sense.

By the way, I removed the API key from your previous message. Even though we’re just testing, you’ll never want to share that publicly, since it allows anyone access to your account’s resources.

19

I have tried adding the single quotes as shown in your message. I have double checked the API Key and found it to be correct based on my account. Here is what I get:

C:\Users\Seth>curl “https://api.pipedream.com/v1/users/me” -H ‘Authorization: Bearer XXX’
{“error”:“record not found”}curl: (6) Could not resolve host: Bearer
curl: (6) Could not resolve host: XXX’

Feel free to remove the API Key again for me. There is very little data in this account at the moment and I included the key again so that you can do some testing to see what you get. I understand that precise syntax is very important. We might be able to cut to the chase if you go ahead and try the access to see if it is working for you. This might save us both some time if you can do that.

Thanks again for “going to the wall” with me on this.
Seth

20

Thanks Seth. That works fine for me, so I still think it’s something with the way the data is getting passed in the HTTP request.

On Windows, you may need to surround the Authorization header section with double quotes. From the error message, you can see that it’s still trying to pass both the Bearer keyword and the API key itself as hosts to which cURL is making an HTTP request (hence the “Could not resolve host: Bearer”) error message.

Since the request works fine for me, this does suggest something about the original request you were making in the other tool didn’t pass the API key correctly, so I’d recommend looking into that more deeply.

21

Found it. I dug through a Devcon session video and found the problem. I am using Filemaker to construct the Curl request and Filemaker does not like the space between Authorization: and Bearer. When I remove that space, the API call works. Syntax like this:

“https://api.pipedream.com/v1/users/me” -H “Authorization:Bearer API_KEY”

Had to be something simple like this since it worked at your end. Thanks again for spending so much time on this with me.

1 Like
22