Automate Nasa TechPort
HumDay reads Nasa TechPort’s own published API description and derives 3 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Nasa TechPort is
TechPort RESTful API
API host: techport.nasa.gov
What HumDay can read from Nasa TechPort
These are the operations a schedule or a trigger can watch.
- GETReturns the swagger specification for the API.
/api - GETReturns a list of available technology project IDs.
/api/projects{.format} - GETReturns information about a specific technology project.
/api/projects/{id}{.format}
How automating Nasa TechPort works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Nasa TechPort account.
- Grant access, then go live. You approve the specific Nasa TechPort operations it may use — and only those.
Automate Nasa TechPort with these
Questions about Nasa TechPort automation
- Can HumDay connect to Nasa TechPort?
- Yes. HumDay reads Nasa TechPort's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 3 operations are documented.
- Do I need to write code to automate Nasa TechPort?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Nasa TechPort account.
- What can HumDay do in Nasa TechPort?
- 0 of the 3 documented operations change something in Nasa TechPort, and 3 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Nasa TechPort account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Nasa TechPort is held behind that approval.
Where this came from
The operations above are read from a published API description for Nasa TechPort at raw.githubusercontent.com/nasa/api-docs/gh-pages/assets/json/Asteroids%20NeoWs. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.