First clean commit

Author: levyitay

CODE_OF_CONDUCT.md

@@ -0,0 +1,7 @@
+As contributors of the Ironsource API Library project, we pledge to respect everyone who contributes by posting issues, updating documentation, submitting pull requests, providing feedback in comments, and any other activities.
+
+Communication through any of Ironsource channels must be constructive and never resort to personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
+
+We promise to extend courtesy and respect to everyone involved in this project regardless of gender, gender identity, sexual orientation, disability, age, race, ethnicity, religion, or level of experience. We expect anyone contributing to the Ironsource API Library project to do the same.
+
+If any member of the community violates this code of conduct, the maintainers of the Ironsource API Library project may take action, removing issues, comments, and PRs or blocking accounts as deemed appropriate.

CONTRIBUTING.md

@@ -0,0 +1,224 @@
+# Contributing to Ironsource API Library
+
+We would love you to contribute to Ironsource API Library!
+As a contributor, here are the guidelines we would like you to follow:
+
+- [Code of Conduct](#coc)
+- [Question or Problem?](#question)
+- [Issues and Bugs](#issue)
+- [Feature Requests](#feature)
+- [Submission Guidelines](#submit)
+- [Commit Message Guidelines](#commit)
+- [Signing the CLA](#cla)
+
+
+## <a name="coc"></a> Code of Conduct
+
+Help us keep Ironsource API Library open and inclusive.
+Please read and follow our [Code of Conduct][coc].
+
+
+## <a name="question"></a> Got a Question or Problem?
+
+Do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests.
+Instead, [contact ironSource support](https://developers.is.com/submit-a-request)
+
+## <a name="issue"></a> Found a Bug?
+
+If you find a bug in the source code, you can help us by [submitting an issue](#submit-issue) to our [GitHub Repository][github].
+Even better, you can [submit a Pull Request](#submit-pr) with a fix.
+
+
+## <a name="feature"></a> Missing a Feature?
+You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub Repository.
+If you would like to *implement* a new feature, please consider the size of the change in order to determine the right steps to proceed:
+
+* For a **Major Feature**, first open an issue and outline your proposal so that it can be discussed.
+  This process allows us to better coordinate our efforts, prevent duplication of work, and help you to craft the change so that it is successfully accepted into the project.
+
+  **Note**: Adding a new topic to the documentation, or significantly re-writing a topic, counts as a major feature.
+
+* **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
+
+
+## <a name="submit"></a> Submission Guidelines
+
+
+### <a name="submit-issue"></a> Submitting an Issue
+
+Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available.
+
+We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it.
+In order to reproduce bugs, we require that you provide a minimal reproduction.
+Having a minimal reproducible scenario gives us a wealth of important information without going back and forth to you with additional questions.
+
+A minimal reproduction allows us to quickly confirm a bug (or point out a coding problem) as well as confirm that we are fixing the right problem.
+
+We require a minimal reproduction to save maintainers' time and ultimately be able to fix more bugs.
+Often, developers find coding problems themselves while preparing a minimal reproduction.
+We understand that sometimes it might be hard to extract essential bits of code from a larger codebase but we really need to isolate the problem before we can fix it.
+
+Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you, we are going to close an issue that doesn't have enough info to be reproduced.
+
+You can file new issues by selecting from our [new issue templates](https://github.com/ironSource/mobile-api-lib-python/issues/new/choose) and filling out the issue template.
+
+
+### <a name="submit-pr"></a> Submitting a Pull Request (PR)
+
+Before you submit your Pull Request (PR) consider the following guidelines:
+
+1. Search [GitHub](https://github.com/ironSource/mobile-api-lib-python/pulls) for an open or closed PR that relates to your submission.
+   You don't want to duplicate existing efforts.
+
+2. Be sure that an issue describes the problem you're fixing, or documents the design for the feature you'd like to add.
+   Discussing the design upfront helps to ensure that we're ready to accept your work.
+
+3. Please review our [Contributor License Agreement (CLA)](#cla) before sending PRs.
+   **By creating a pull request you accept the *Contributor License Agreement (CLA)***
+
+4. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) the angular/angular repo.
+
+5. In your forked repository, make your changes in a new git branch:
+
+     ```shell
+     git checkout -b my-fix-branch main
+     ```
+
+6. Create your patch, **including appropriate test cases**.
+
+
+7. Run the unit tests
+    ```shell
+    npm run test
+    ```
+    ***optional:***
+    If you have your own ironSource credentials that you wish to test with add them to your local .env
+    ```shell
+    API_CI_SECRET=
+    API_CI_TOKEN=
+    API_CI_USER=
+    ```
+    or
+     ```shell
+    DEMO_ACCOUNT_SECRET=
+    DEMO_ACCOUNT_TOKEN=
+    DEMO_ACCOUNT_USER=
+    ```
+    
+    then run:
+    ```shell
+    npm run integrationTest
+    ```
+
+8. Run lint:
+    ```shell
+    npm run lint
+    ```
+
+9. Commit your changes using a descriptive commit message that follows our [commit message conventions](#commit).
+   Adherence to these conventions is necessary because release notes are automatically generated from these messages.
+
+     ```shell
+     git commit --all
+     ```
+   Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
+
+10. Push your branch to GitHub:
+
+    ```shell
+    git push origin my-fix-branch
+    ```
+
+11. In GitHub, send a pull request to `ironSource/mobile-api-lib-python:main`.
+
+### Reviewing a Pull Request
+
+The Ironsource API Library team reserves the right not to accept pull requests from community members who haven't been good citizens of the community. Such behavior includes not following the [code of conduct][coc]
+
+#### Addressing review feedback
+
+If we ask for changes via code reviews then:
+
+1. Make the required updates to the code.
+
+2. Re-run the Ironsource API Library test to ensure tests are still passing.
+
+3. Create a fixup commit and push to your GitHub repository (this will update your Pull Request):
+
+    ```shell
+    git commit --all --fixup HEAD
+    git push
+    ```
+
+That's it! Thank you for your contribution!
+
+
+
+## <a name="commit"></a> Commit Message Format
+
+Please follow the [conventional-commits format][commit]
+
+Commit format:
+```
+<type>(<scope>): <short summary>
+  │       │             │
+  │       │             └─⫸ Summary in present tense. Not capitalized. No period at the end.
+  │       │
+  │       └─⫸ Commit Scope: component_name|service_name|feature_name|....
+  │
+  └─⫸ Commit Type: build|ci|feat|fix|refactor|test|perf
+```
+
+The `<type>` and `<summary>` fields are mandatory, the `(<scope>)` field is optional.
+
+
+##### Type
+
+Must be one of the following:
+
+* **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+* **ci**: Changes to our CI configuration files and scripts (example scopes: Circle, BrowserStack, SauceLabs)
+* **feat**: A new feature
+* **fix**: A bug fix
+* **perf**: A code change that improves performance
+* **refactor**: A code change that neither fixes a bug nor adds a feature
+* **test**: Adding missing tests or correcting existing tests
+
+
+##### Scope
+The scope should be the name of the npm module affected
+
+
+##### Summary
+
+Use the summary field to provide a succinct description of the change:
+
+* use the imperative, present tense: "change" not "changed" nor "changes"
+* don't capitalize the first letter
+* no dot (.) at the end
+
+
+#### <a name="commit-body"></a>Commit Message Body
+
+
+Explain the motivation for the change in the commit message body. This commit message should explain _why_ you are making the change.
+You can include a comparison of the previous behavior with the new behavior in order to illustrate the impact of the change.
+
+
+
+### Revert commits
+
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
+
+The content of the commit message body should contain:
+
+- information about the SHA of the commit being reverted in the following format: `This reverts commit <SHA>`,
+- a clear description of the reason for reverting the commit message.
+
+
+
+
+[github]: https://github.com/ironSource/mobile-api-lib-python
+[coc]: https://github.com/ironSource/mobile-api-lib-python/blob/main/CODE_OF_CONDUCT.md
+[cla]: https://github.com/ironSource/opensource-contributor-license-agreement
+[commit]: https://www.conventionalcommits.org/en/v1.0.0/

MANIFEST.in

@@ -0,0 +1,6 @@
+include README.md
+include requirements.txt
+graft ironsource_api
+recursive-exclude * *.py[co]
+include versioneer.py
+include ironsource_api/_version.py

README.md

@@ -0,0 +1,75 @@
+
+# ironsource_api_python
+![Test And Lint](https://github.com/ironSource/mobile-api-lib-python/actions/workflows/deploy.yml/badge.svg)
+
+## Installation
+
+This module is installed via pip:
+
+```
+pip install ironsrc_mobile_api
+```
+
+## Simple Example:
+```python
+import os
+from ironsource_api.ironsource_api import IronSourceAPI
+from ironsource_api.promote_api import Metrics, Breakdowns
+
+ironsrc_api = IronSourceAPI()
+
+ironsrc_api.set_credentials(API_USER, API_TOKEN,API_SECRET)
+
+#Get Monetization Data
+res = ironsrc_api.monetize_api().get_monetization_data(start_date='2020-01-01', end_date='2020-01-01')
+
+
+#Get Advertiser Statistics
+bytes_io = ironsrc_api.promote_api().get_advertiser_statistics('2020-10-03','2020-10-04',
+        [Metrics.Impressions,Metrics.Clicks,Metrics.Installs],
+        [Breakdowns.Application,Breakdowns.Day],response_format='csv')
+
+line = bytes_io_r.readline()
+
+while len(line) > 0:
+    print(line)
+    line = bytes_io_r.readline()
+
+bytes_io_r.close()
+
+
+
+```
+####  Authentication
+Before starting to use the API make sure to get the credentials from ironSource dashboard.
+![Account Cred](https://developers.ironsrc.com/wp-content/uploads/2019/01/1-1.png)
+
+And set the Access Key, Secret Key and Refresh Token: 
+<a id="ironsource_api.IronSourceAPI.set_credentials"></a>
+
+#### set\_credentials
+
+```python
+def set_credentials(user: str, token: str, secret: str)
+```
+
+sets credentials for the APIs
+
+
+<br>
+## Modules
+
+* [IronSourceAPI](#ironsource_api.IronSourceAPI)
+    * [monetize\_api](docs/monetize_api.md)
+    * [promote\_api](docs/promote_api.md)
+
+
+<br>
+
+## Contributing:
+Please follow contribution [guide](/CONTRIBUTING.md)
+
+## Dependencies
+* [requests](https://github.com/psf/requests)
+* [httpx](https://github.com/encode/httpx)
+* [pydash](https://github.com/dgilland/pydash)

dev_requirements.txt

@@ -0,0 +1,8 @@
+pytest~=6.2.5
+pytest-ordering~=0.6
+pylint~=2.7.4
+pytest-dotenv~=0.5.2
+versioneer~=0.22
+pytest-mock~=3.8.2
+pytest-asyncio~=0.19.0
+pytest-timeout~=2.1.0