Migration Pluto into Spectrum¶
Overview¶
Migration from the Pluto-I
endpoint into Inno-Spectrum
Note for migration process:
-
Supported both API until the transfer has been processed and confirmed by Project Manager related.
-
The timerange for supported estimated for 3-6 month in advanced for the
Pluto-I
service -
Recommended to transfer to new-official API with new features included
-
For the
Inno-Spectrum
, we will follow method to suspend the/pluto
prefix path
Time | Changed | Status |
---|---|---|
2024-01 | Deprecate the route | Supported |
2024-02 | Hide all | Supported |
2024-03 | Remove route | Unsupported |
What changed¶
Changed specification of RestfulAPI service ¶
The origin URL of service:
Pluto-I | Inno-Spectrum |
---|---|
dapi.innotech.vn | api.data.innotech.vn |
For network, the client network required to whitelist our exposure global IP at:
Pluto-I | Inno-Spectrum |
---|---|
IP 34.111.3.169 | IP 34.149.39.90 |
Changed the route path related with collections endpoint¶
For the previous usage, here are the list of transfered
Pluto-I | Inno-Spectrum |
---|---|
/stocks/detail | /pluto/profile |
/stocks/eod | /pluto/quote |
/stocks/adjust | /pluto/adjustment/symbol |
/world/index | /pluto/world/index |
FAQ¶
Is it the same configure the endpoint¶
Yes. It's the same on the following component:
-
Query parameters
-
The payload configuration
-
The returned payload
Is the limit=-1
still supported?¶
The limit=-1
still supported but this case will harm our services by returned large payload. It's can lead to 500 status based on services specficiation (RAM). So recommendation to not use this in advanced.
Supported unauthentication?¶
Currently yes. For only pluto
route endpoint. Please contact @bao.truong to has API account.