|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Portfolio Optimizer (ranked 350 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/Portfolio_Optimizer_bcd759b9_7fa5_40ef_8bb2_413a7cf64b19_yaml.yamlGENERAL INFORMATION
Portfolio Optimizer is a Web API to optimize the composition of investment portfolios (collection of financial assets such as stocks, bonds, ETFs, crypto-currencies) using modern portfolio theory-like algorithms (mean-variance, etc.).
API General Information
Portfolio Optimizer is based on REST for easy integration, uses JSON for the exchange of data and uses the two most common HTTP verbs (GET
, POST
) to represent the actions.
Portfolio Optimizer is also as secured as a Web API could be:
- 256-bit HTTPS Encryption
- No usage of cookies
- No usage of personal data
API Headers
The following HTTP header(s) are required when calling Portfolio Optimizer endpoints:
Content-type: application/json
This header spec
...
Contact
- Name: Support
- Name: contact@portfoliooptimizer.io
- Contact API maintainers
License
- Name: Apache 2.0
- See License
SECURITY 4/5
The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.
- OWASP issues detected: API7:2023
PERFORMANCE 4/5
The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.
- The median response time of the API is 72.1 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/5
The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.
- Self compliance: response objects matched the declared response types.
- Server errors: the server did not return any 5xx error.
DESIGN 4/5
The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.
- Respects OpenAPI 3.0.1 schema specification.
- Contains comments and summaries.
- Contains examples.
- Does not contain duplicated objects.
Popularity 0/5
The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!